second attempt at catching stale PRs #10648
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The first one didn't fire, despite there being 3 PRs that should have matched. This one tries to match the queue failure itself instead of checking for lack of activity.
geekosaur
force-pushed
the
mergify-stuck-2
branch
from
4c7d91f to
cacefa4
Compare
Kleidukos
approved these changes
Dec 19, 2024
|
Not sure it's necessary at this point; the first one actually works, it just needs its wait time cranked down a bit (it's 5 days currently). |
|
5 days isn't bad! But in any case it'd be good to either merge or close! |
|
I vote for closing, since the first one is actually working so there's no point in trying the somewhat dubious second. |
|
SGTM, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The first one didn't fire, despite there being 3 PRs that should have matched. This one tries to match the queue failure itself instead of checking for lack of activity.
Please read Github PR Conventions and then fill in one of these two templates.
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR:
Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).Mergify only readsmergify.ymlonmaster