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

add "ready and waiting" Mergify label #10223

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

geekosaur
Copy link
Collaborator

The bot can use this to announce PRs that are entering the 2-day waiting period.

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:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions). —not relevant as it is only read on master

@geekosaur geekosaur force-pushed the mergify-ready-label branch 2 times, most recently from f987f78 to 7e27303 Compare July 23, 2024 02:30
@ffaf1
Copy link
Collaborator

ffaf1 commented Jul 23, 2024

What if then I comment on the PR? Will there be another announcement?

@geekosaur
Copy link
Collaborator Author

No, because I don't track comments and the label already exists. AIUI the point is to tell people that it's their last chance to review the PR and add any comments.

@geekosaur
Copy link
Collaborator Author

This also means there won't be a re-announcement if someone requests changes at that point and those changes are made, unless someone manually removes the label. It's probably possible to make Mergify manage that case itself, but I'm not sure it's worth doing.

@geekosaur
Copy link
Collaborator Author

geekosaur commented Jul 23, 2024

BTW this isn't necessarily done. On two reviews, the new rules should trigger… but I'm unclear on whether the "(pull_request)" suffix needs to be part of the CI checks, so it may not fire. (ETA: turns out Mergify injects those rules into its own, so I could see from the Mergify tab of CI what the labels needed to be.)

@geekosaur geekosaur force-pushed the mergify-ready-label branch 3 times, most recently from 3cbb79e to 0d96340 Compare July 24, 2024 01:11
@jasagredo jasagredo self-requested a review August 1, 2024 17:45
@geekosaur
Copy link
Collaborator Author

@jasagredo, I think this is just waiting on your self-assigned review? Is this a bad time?

@geekosaur geekosaur force-pushed the mergify-ready-label branch from 0d96340 to f5a2c2e Compare August 24, 2024 15:16
Copy link
Collaborator

@jasagredo jasagredo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@geekosaur geekosaur added the merge me Tell Mergify Bot to merge label Aug 26, 2024
@mergify mergify bot added the merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days label Aug 28, 2024
The bot can use this to announce PRs that are entering the 2-day
waiting period.
@Mikolaj Mikolaj force-pushed the mergify-ready-label branch from f5a2c2e to 9b55b2e Compare August 28, 2024 10:53
@mergify mergify bot merged commit c2ce3a6 into haskell:master Aug 28, 2024
50 checks passed
@geekosaur geekosaur deleted the mergify-ready-label branch September 3, 2024 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants