feat(skin) rename vivo-new into vivo, and introduce vivo-evolution (copy ov vivo-new)#357
Merged
Merged
Conversation
brtbrt
changed the title
- Add vivo-evolution icon set as a copy of the current vivo set - Register vivo-evolution in the figma export config, package scripts and release workflow - Regenerate ICON_TABLE.md and README.md so Vivo links resolve to icons/vivo and add the vivo-evolution column
yceballost
requested changes
Jul 10, 2026
# Conflicts: # .github/workflows/figma-export.yml # ICON_TABLE.md # README.md
yceballost
previously approved these changes
Jul 13, 2026
yceballost
reviewed
Jul 13, 2026
yceballost
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #1595
Summary
vivo-newicon set tovivo(the previousvivoskin is replaced andvivo-newdisappears).vivo-evolutionskin, initialized as an exact copy of the currentvivoset.vivo-evolutionin the Figma export config (brands.config.js), thepackage.jsonexport scripts, and the release workflow (figma-export.yml).ICON_TABLE.mdandREADME.mdso every Vivo image link resolves toicons/vivoand thevivo-evolutioncolumn is added.Required actions before merging
The
vivo-evolutionbrand is wired to a dedicated Figma source, currently using placeholders. These must be replaced with the real values before the export workflow can run for this brand:defaultFileId: "REPLACE_WITH_VIVO_EVOLUTION_FILE_ID"in.github/scripts/figma-export/brands.config.jswith the real Vivo-evolution Figma file id.VIVO_EVOLUTION_FILE_URLin.github/workflows/figma-export.ymlwith the real Vivo-evolution Figma file URL.VIVO_EVOLUTION_FIGMA_IDsecret/variable to thefigma-importGitHub environment (the export driver readsprocess.env[figmaEnv]and falls back todefaultFileId).Notes
The
icons/vivo-evolutionfiles are currently a byte-for-byte copy oficons/vivo. Once the brand points to its real Figma file and the export runs, the two sets will diverge as intended.