fix: contracts auto-deploy GitHub Actions workflow#1238
Merged
Conversation
999e799 to
3c57089
Compare
if workflow files are updated on main, GitHub rejects the push. with this, we can simplify our solution and simply use GHA permissioning instead of having to create a PAT.
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.
This fixes our GitHub Actions workflow to auto-deploy contracts to Calibnet when changes are detected. This has been failing for some months and we never got around to fixing it. New users kept tripping up regularly when following the quickstart tutorial @ docs.ipc.space, which instructs them to deploy their subnet against the existing framework contracts on Calibnet. However, those contracts were outdated leading to severe compatibility issues.
While fixing this, I also: