So using this GitLab sync, we can create a token package that is synced to Tokens Studio. Every time token updates and the changes pushed to GitLab, we can make a new release and the consuming apps of this token package can use the new/updated tokens. Is that the whole point? This doesn't mean it removes the necessity of having a dedicated token package and consume straight from the GitLab repo, correct?
If you intend to use this in development I’d still recommend publishing a dedicated token package. In the described flow, a designer can make changes in Figma. These changes can then be created into a merge request (MR), which, when merged, results in a new version of the package being published. - Keegan
![[DRIP] ‘Love, Maybe’ PREVIEW](http://i.ytimg.com/vi/U7hwHp95m1k/mqdefault.jpg)
So using this GitLab sync, we can create a token package that is synced to Tokens Studio. Every time token updates and the changes pushed to GitLab, we can make a new release and the consuming apps of this token package can use the new/updated tokens. Is that the whole point? This doesn't mean it removes the necessity of having a dedicated token package and consume straight from the GitLab repo, correct?
If you intend to use this in development I’d still recommend publishing a dedicated token package. In the described flow, a designer can make changes in Figma. These changes can then be created into a merge request (MR), which, when merged, results in a new version of the package being published. - Keegan
@@TokensStudio gotcha. Thanks for the clarification!