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

docs: Make it clear that the Setup step must be ran before the Execue step #1068

Merged

docs: Make it clear that the Setup step must be ran before the Execut…

f5fe675
Select commit
Loading
Failed to load commit list.
Merged

docs: Make it clear that the Setup step must be ran before the Execue step #1068

docs: Make it clear that the Setup step must be ran before the Execut…
f5fe675
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 10, 2024 in 1s

1 rule matches

⚠️ The pull request has been merged by @arturcic

✅ Rule: Thank contributor (comment)

  • -author~=^dependabot(|-preview)\[bot\]$
  • merged

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: Automatic approve on dependabot PR (review)

  • author~=^dependabot(|-preview)\[bot\]$

Rule: Automatic merge on dependabot PR after success CI (merge)

  • -closed [📌 merge requirement]
  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=build (macos-latest)
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #commits-behind=0
  • #commits-behind=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
  • check-success=build (ubuntu-latest)
  • check-success=build (windows-latest)
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=build (windows-latest)
    • check-neutral=build (windows-latest)
    • check-skipped=build (windows-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success=build (ubuntu-latest)
    • check-neutral=build (ubuntu-latest)
    • check-skipped=build (ubuntu-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success=actions (build macos-latest)
    • check-neutral=actions (build macos-latest)
    • check-skipped=actions (build macos-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success=actions (build windows-latest)
    • check-neutral=actions (build windows-latest)
    • check-skipped=actions (build windows-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success=actions (build ubuntu-latest)
    • check-neutral=actions (build ubuntu-latest)
    • check-skipped=actions (build ubuntu-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success=build (macos-13)
    • check-neutral=build (macos-13)
    • check-skipped=build (macos-13)
  • any of: [🛡 GitHub branch protection]
    • check-success=build (macos-14)
    • check-neutral=build (macos-14)
    • check-skipped=build (macos-14)
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