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

Revert "have Mergify insist on all-green CI" #10465

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

geekosaur
Copy link
Collaborator

It didn't do what was intended, and apparently Mergify is now tripping over its own feet about it (see #10425). May require manual merge.

This reverts commit d9c2b40.

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).

It didn't do what was intended, and apparently Mergify is now
tripping over its own feet about it.

This reverts commit d9c2b40.
.github/mergify.yml Show resolved Hide resolved
since Mergify can't do it or we wouldn't need the label
@geekosaur geekosaur added merge me Tell Mergify Bot to merge and removed attention: needs-review labels Oct 16, 2024
@mergify mergify bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days ready and waiting Mergify is waiting out the cooldown period labels Oct 16, 2024
@mergify mergify bot merged commit ebe9f55 into haskell:master Oct 16, 2024
49 checks passed
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 priority: high 🔥 ready and waiting Mergify is waiting out the cooldown period
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants