Add convention on asset retention #11381
Merged
Conversation
This file contains 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
**Why** While authoring a different feature, it became apparent that we do not store multiple variants of asset "just in case". We can re-export from our authoring tools (i.e., Figma) if need be. This adds a note why we do not do this for developers from the future. [skip changelog]
|
@aduth - here's that tiny PR I said I'd make on our how we author and version control assets. |
colter-nattrass
pushed a commit
that referenced
this pull request
Oct 23, 2024
**Why** While authoring a different feature, it became apparent that we do not store multiple variants of asset "just in case". We can re-export from our authoring tools (i.e., Figma) if need be. This adds a note why we do not do this for developers from the future. [skip changelog]
MrNagoo
pushed a commit
that referenced
this pull request
Oct 25, 2024
**Why** While authoring a different feature, it became apparent that we do not store multiple variants of asset "just in case". We can re-export from our authoring tools (i.e., Figma) if need be. This adds a note why we do not do this for developers from the future. [skip changelog]
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.
Why
While authoring a different feature, it became apparent that we do not store multiple variants of asset "just in case". We can re-export from our authoring tools (i.e., Figma) if need be.
This adds a note why we do not do this for developers from the future.
[skip changelog]