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

README.md: update Build Status #223

Merged
merged 1 commit into from
May 30, 2024

README.md: update Build Status

eaf4a4e
Select commit
Loading
Failed to load commit list.
Merged

README.md: update Build Status #223

README.md: update Build Status
eaf4a4e
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 30, 2024 in 0s

2 potential rules

⚠️ The pull request has been merged by @innobead

Rule: Automatically merge PRs (merge)

  • #approved-reviews-by>=2
  • -closed [📌 merge requirement]
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #commits-behind=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • approved-reviews-by=@longhorn/maintainer
  • check-success="Build binaries"
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=DCO
    • check-neutral=DCO
    • check-skipped=DCO

Rule: Ask to resolve conflict (comment)

  • conflict

💖  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: Automatically merge Renovate PRs (merge)

  • -closed [📌 merge requirement]
  • author = renovate[bot]
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #commits-behind=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success="Build binaries"
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=DCO
    • check-neutral=DCO
    • check-skipped=DCO

Rule: Automatically approve Renovate PRs (review)

  • author = renovate[bot]
  • check-success="Build binaries"
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