Update Chromatic deployment action, to only deploy when needed. #642
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
Refactored the Chromatic deployment GitHub Action to enhance deployment efficiency by ensuring actions only run when necessary. Up until now, it triggered on every single push, regardless if the push was made against an active pull request or not. The workflow now triggers on push events for the main, develop, and release/* branches, and on specific pull_request events. Added concurrency control to prevent duplicate workflows from running simultaneously by canceling in-progress actions if a new relevant event occurs. These changes improve deployment efficiency, consistency, and hopefully means we won't exceed the tokens as often.
rasben
force-pushed
the
chromatic-action-tweak
branch
from
b7d0e75 to
6ab7420
Compare
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.
Update Chromatic deployment action, to only deploy when needed.
Refactored the Chromatic deployment GitHub Action to enhance deployment
efficiency by ensuring actions only run when necessary.
Up until now, it triggered on every single push, regardless if the push
was made against an active pull request or not.
The workflow now triggers on push events for the main, develop, and
release/* branches, and on specific pull_request events. Added
concurrency control to prevent duplicate workflows from running
simultaneously by canceling in-progress actions if a new relevant event
occurs. These changes improve deployment efficiency, consistency, and
hopefully means we won't exceed the tokens as often.
https://reload.zulipchat.com/#narrow/stream/240325-DDF/topic/chromatic.20og.20push