Add dry_run input option
#204
Conversation
This is useful if you don't actually want to release, but you're just interested in whether or not a release would be created. Useful to gate a secondary job with an environment, without creating requests for each and every change. Fixes release-plz#200
| If the input `command` is left unspecified (and so both `release` and `release-pr` are ran), | ||
| the `--dry-run` flag is only added to the `release` command | ||
| (the flag isn't added to the `release-pr` command). | ||
| Useful if you're only interested in whether or not a release (pr) would be created." |
There was a problem hiding this comment.
how do you determine if a release-pr will be created? can you explain more?
|
can you also open a PR for https://github.com/release-plz/release-plz/blob/main/website/docs/github/input.md ? |
|
- uses: release-plz/[email protected]
with:
command: release-dryrunI know this doesn't cleanly map to CLI Another alternative is to just have an "untyped" - uses: release-plz/[email protected]
with:
command: release
options: --dry-runFYI I'm interested in this (or rather #200) since a conditional |
|
I prefer having the 2 inputs with the 4 combinations instead of |
3 participants
This is useful if you don't actually want to release, but you're just interested in whether or not a release would be created. Useful to gate a secondary job with an environment, without creating requests for each and every change.
Fixes #200