-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 --dry-run flag to release tooling #563
Comments
I would let the tagging happen so you can check that the tags are okay. Would be nice if it outputted to stdout all the missing 'cleanup' commands. Like
|
What if instead for the operations that we skip we send a console.log call with grey coloring. It's easy to forget to remove those tags. |
I'm not too worried about the temp folders hanging around, they are already in the .gitignore, and we remove those folders before we do anything with them. |
Actually, if we can send all the commands in grey fo the dry run that be perfect (maybe add a verbose option for that?) |
I can do that as well |
Add `--dry-run` and `--verbose` options to release process to facilitate some means to test the release process. Also fixes a few bugs found in the existing process along the way. Closes #563
The current release tooling is currently sketchy to test, especially since it's usage is very public in nature. Adding a
--dry-run
flag that simply skips any steps that tag, push, commit, or publish. An additional thing to skip would be the final cleanup that removes temporary folders. This way you can verify that the contents of these temporary folders are as you expect.Original conversation for this from #547
The text was updated successfully, but these errors were encountered: