-
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
feat: break refresh
opt into bless
and update
#261
Conversation
@@ -380,7 +385,7 @@ pub async fn gauntlet(args: Args) -> Result<()> { | |||
|
|||
println!("\nTotal analysis time: {total_time:?}"); | |||
|
|||
if args.refresh { | |||
if args.bless || args.update { |
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.
Should this only fire on --bless
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.
No, we need to save the new diagnostics (and new hashes) back to the relevant config file when --update
is passed. Otherwise --update
would be a no-op that fails whenever something changed.
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.
After the above is addressed, looks good to me.
Co-authored-by: Clay McLeod <3411613+claymcleod@users.noreply.github.com>
Describe the problem or feature in addition to a link to the issues.
closes #226
Before submitting this PR, please make sure:
changes (when appropriate).
CHANGELOG.md
(see"keep a changelog" for more information).