-
Notifications
You must be signed in to change notification settings - Fork 701
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
Do not print "up to date" unless running build #8569
Conversation
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.
LGTM, thanks! Tests will have to be updated so it doesn't need more tests, I think. We need a changelog though.
@mergify refresh |
✅ Pull request refreshed |
@mergify requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
@cbclemmer just a heads-up: normally you don't need to do anything explicit with Mergify. Just put the label merge-me (or squash+merge) when you think it's ready. What currently blocks this PR is a missing second reviewer. |
@ulysses4ever There was some kind of build error with the CI, I was just trying to get it to run again. |
All tests are passing |
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.
LGTM
* do not print "up to date" unless running build * Update cabal-tests * Add changelog * Remove accidentally added test generated files Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
closes #4994
"Up to date" will not print unless the
build
command is run.I expect this to break tests that use the
build
andrun
commands so I'll update them based on the CI results. This should in effect test the PR itself to keep it from regressing.Please include the following checklist in your PR:
Please also shortly describe how you tested your change. Bonus points for added tests!