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: Add Metal L2 and Metal L2 testnet #932

Merged
merged 6 commits into from
Sep 20, 2024

Merge pull request #3 from MetalLayer2/add-metall2

5d1641d
Select commit
Loading
Failed to load commit list.
Merged

feat: Add Metal L2 and Metal L2 testnet #932

Merge pull request #3 from MetalLayer2/add-metall2
5d1641d
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 20, 2024 in 3s

3 faulty rules and 2 rules match and 2 potential rules

⚠️ The pull request has been merged by @nitaliano

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: remove outdated reviews for non trusted authors (dismiss_reviews)

  • all of:
    • author!=@ecopod ⚠️ Team @ecopod does not exist
    • base=master

Rule: Say hi to contributors if they are not part of the regularcontributors team (comment)

  • author!=@regularcontributors ⚠️ Team @regularcontributors does not exist

Rule: Say thanks (comment)

  • author!=@regularcontributors ⚠️ Team @regularcontributors does not exist
  • merged

Rule: Automatic merge on approval (queue)

  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • all of:
    • #approved-reviews-by>=1
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved=0
    • base==master
    • label!=do-not-merge
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]

Rule: Ask to resolve conflict (comment, label)

  • conflict

✅ Rule: Remove conflicts label when conflicts gone (label)

  • -conflict

✅ Rule: Notify author when merge queue failed (comment)

  • check-failure=Queue: Embarked in merge train

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