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

feat: downtime detector command #293

Closed
wants to merge 4 commits into from

Merge branch 'umee' into woz/add-downtime-detector

e73de12
Select commit
Loading
Failed to load commit list.
Closed

feat: downtime detector command #293

Merge branch 'umee' into woz/add-downtime-detector
e73de12
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 29, 2024 in 2s

no rules match, no planned actions


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

🚀  You can help us by becoming a sponsor!


3 not applicable rules

Rule: Automatic merge on approval (queue)

  • #approved-reviews-by>=1
  • -draft [📌 queue requirement]
  • base=main
  • label=A:Automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • #review-threads-unresolved=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=test-unit
        • check-neutral=test-unit
        • check-skipped=test-unit
      • any of: [🛡 GitHub branch protection]
        • check-success=Run PR Title Linter
        • check-neutral=Run PR Title Linter
        • check-skipped=Run PR Title Linter
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: Automatic merge on approval (merge)

  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #commits-behind=0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
  • label=A:Automerge
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=test-unit
    • check-neutral=test-unit
    • check-skipped=test-unit
  • any of: [🛡 GitHub branch protection]
    • check-success=Run PR Title Linter
    • check-neutral=Run PR Title Linter
    • check-skipped=Run PR Title Linter

Rule: Backport changes to umee branch (backport)

  • base=main
  • label=S:backport/umee
  • merged [📌 backport requirement]
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