-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add actions #10
base: main
Are you sure you want to change the base?
Add actions #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤟 thank you! a few suggestions only
README.md
Outdated
- `fork` - deploy and test on forked network | ||
- `deploy` - deploy on live network | ||
- `verify` - verify on live network | ||
- `check` - check on live network |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the difference between verify
and check
maybe not so clear for external viewers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is check
== test
or what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 'verify' step is about contracts source code verification. Since it is somewhat unstable (requiring a wait for the block explorer to recognize the address as a contract and multiple attempts), I have placed it in a separate action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's name it publish-sources
?
|
||
function parseCmdLineArgs() { | ||
program | ||
.argument("<config-path>", "path to .yaml config file") | ||
.option("--onlyCheck", "only check the real network deployment") | ||
.option("--onlyForkDeploy", "only deploy to the forked network") | ||
.option("--actions [actions...]", "list of actions: fork deploy verify check", ["all"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From this line the format of the list isn't clear. Let's provide an example, smth like:
"list of actions: 'fork' 'deploy' 'verify' 'check'". E.g. "[deploy,verify,check]". Default ["all"]
Add possibility to provide actions instead of steps in a format: fork, deploy, verify, check or all