Skip to content
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

RFC: Dry run improvements #247

Closed
wants to merge 2 commits into from
Closed

Conversation

joestringer
Copy link
Member

See commit messages for more details:

  • In --dry-run mode, ask before every execution
  • Continue failing steps in --dry-run mode

This is intended to slow down the overall process and ensure that when
you run these commands with --dry-run, you as a user can more easily
understand exactly all of the mutable steps that are being made.

There's a slight weakness here, which is that any change that the binary
makes directly in Go will not be covered by this. But it covers a fair
amount (git invocations, sending PRs).

Signed-off-by: Joe Stringer <[email protected]>
In dry-run mode, we shouldn't be making any mutable changes, so it
should be safe to report errors and then continue to the next step.

Example use case: The first stage of step 1 failed due to release
blockers being opened. I wanted to _also_ find out about the status of
the vulnerability scanners, but previously the command would stop before
the latter stage.

Signed-off-by: Joe Stringer <[email protected]>
@joestringer
Copy link
Member Author

joestringer commented Jul 25, 2024

I'm a little bit paranoid about dry run mode due to #245 , but this might be going too far. I found it quite useful while preparing #244 since this is the first time we're using this tool for a minor release, but I'm also not entirely convinced that this is the right UX. We could adopt all, none, or a subset of the proposals in this PR.

@joestringer joestringer closed this Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant