-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support dry-run mode #19
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Especially for testing the script of a release build, a "dry-run-mode" would be useful.
For releases, the publishing of the release could be skipped - so that the draft release can still be verified.
For maven central, the automatic release of the staging repo can be skipped, then we are left with a staging repo, that can be used for testing and dropped afterwards.
File uploads to sourceforge/pmd-code.org need to be skipped (binaries, regression tester, docs).
Blog post on sourceforge can be created as draft, but the publish can be skipped.
The text was updated successfully, but these errors were encountered: