ᛘ Support branches in Figma
For community members on Figma plans that support branching, they want to do work with the plugin on a Figma branch and when they merge the branch into main have their token work come with them.
They also want changes made to tokens on their main file to be reflected on the branch they are working on.
😬 The reality
Historically this feature was blocked by Figma limitations with the data exposed to the plugin.
💬 Feedback that is valuable
How does this issue impact your day-to-day workflow?
What workarounds do you have?
↔ Related topics
TBD → Jump to post
Log in to comment and vote
Comments2
Keegan (Tokens Studio)
Feb 12, 2025
Add Version Tracking for Tokens in Figma Components:
A team is encountering issues with managing token versions in Figma components, particularly during branch merges and releases. The lack of visibility into which token versions are applied to components has led to inconsistencies, especially when Figma experiences unexpected crashes. This problem is worse during simultaneous releases of their library on Figma and tokens on GitHub.
Current Process:
1. Create a branch in Figma to apply changes for the upcoming release.
2. Add and apply relevant tokens.
3. Merge branches and release the library version on Figma and tokens on GitHub simultaneously.
Problem:
• No visibility or tracking of token versions applied to components.
• Inconsistencies arise when Figma crashes during merges, causing some components to not save the latest token updates.
Proposed Solution:
A version tracking feature for tokens within Figma components to ensure consistency and provide visibility into which token versions are applied.
‼️ Important:
We will have to check the possibility of something like this with Figma’s API.
Sam - Tokens Studio
Apr 4, 2024
Github Issues
1458
1413