chore: manual action for verifying deployments #758
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
Codecov ReportBase: 91.59% // Head: 91.59% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## dev #758 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 42 42
Lines 1999 1999
Branches 361 361
=======================================
Hits 1831 1831
Misses 168 168
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
pcarranzav
previously approved these changes
Dec 6, 2022
pcarranzav
approved these changes
Dec 6, 2022
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.
Adds a manual github action for verifying deployments. The inputs to the action are the list of contracts to verify and their network. From that, the deployment addresses are picked up from
addresses.json.The verify job will use Defender's API to check that the compiled artifacts at that branch match the ones deployed. An example run can be seen here.
These results can also be manually checked on Defender after the verification was run.
This workflow requires defining the repository secrets:
DEFENDER_API_KEYDEFENDER_API_SECRETINFURA_KEY