CI: Push wasm commit on changes only #603
Merged
Conversation
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
When rerunning the deploy wasm CI, previously successful jobs may fail due to a reproducible error: nothing to commit, working tree clean Error: Process completed with exit code 1. This occurs because the successful deployment has already committed the changes. To prevent this, the workflow should check whether there are any staged changes before attempting to commit. If there’s nothing to commit, skip the push step. Otherwise, proceed with committing and pushing the new changes.
|
Bito Automatic Review Skipped - Files Excluded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When rerunning the deploy wasm CI, previously successful jobs may fail due to a reproducible error:
nothing to commit, working tree clean
Error: Process completed with exit code 1.
This occurs because the successful deployment has already committed the changes. To prevent this, the workflow should check whether there are any staged changes before attempting to commit. If there’s nothing to commit, skip the push step. Otherwise, proceed with committing and pushing the new changes.
The error can be observed in this ci.