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.

Sign up for GitHub

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

Print out which project file we're using by default (fix #8519) #18

Closed
wants to merge 1 commit into from

Print out which project file we're using by default (fix #8519)

321aa6e
Select commit
Loading
Failed to load commit list.
Closed

Print out which project file we're using by default (fix #8519) #18

Print out which project file we're using by default (fix #8519)
321aa6e
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 5, 2024 in 1s

6 potential rules

Rule: Wait for 2 days before validating merge (label)

  • #approved-reviews-by>=2
  • any of:
    • label=merge me
    • label=merge+no rebase
    • label=squash+merge me
  • any of:
    • updated-at<2 days ago
    • label=priority: high :fire:

Rule: Waiting out merge delay (used by bot) (label)

  • #approved-reviews-by>=2
  • -closed
  • check-success=Validate post job
  • check-success=docs/readthedocs.org:cabal
  • any of:
    • label=merge me
    • label=merge+no rebase
    • label=squash+merge me
  • #changes-requested-reviews-by=0
  • -draft
  • base=master
  • check-success=Bootstrap post job
  • check-success=Doctest Cabal
  • check-success=Meta checks
  • check-success=fourmolu
  • check-success=hlint

Rule: Put pull requests in the rebase+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • label=merge delay passed
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

Rule: Put pull requests in the squash+merge queue (queue)

  • #approved-reviews-by>=2
  • -closed [📌 queue requirement]
  • label=merge delay passed
  • label=squash+merge me
  • #commits-behind=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue squash-merge]

Rule: Merge "merge+no rebase" pull requests directly (without a queue) (merge)

  • #approved-reviews-by>=2
  • -closed [📌 merge requirement]
  • label=merge delay passed
  • label=merge+no rebase
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -label~=^blocked:
  • base=master
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Label backports as such (label)

  • body~=automatic backport
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

4 not applicable rules

Rule: Put release branch pull requests in the rebase+merge queue (queue)

  • #approved-reviews-by>=2
  • -body~=backport
  • -closed [📌 queue requirement]
  • base!=master
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

Rule: Put release branch pull requests in the squash+merge queue (queue)

  • #approved-reviews-by>=2
  • -body~=backport
  • -closed [📌 queue requirement]
  • base!=master
  • label=squash+merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue squash-merge]

Rule: Put backports in the rebase+merge queue (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • base!=master
  • label=merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • body~=backport
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

Rule: Put backports in the squash+merge queue (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • base!=master
  • label=squash+merge me
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=^blocked:
  • body~=backport
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue squash-merge]
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

View more details on Mergify