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

build(deps): bump tgymnich/fork-sync from 1.8 to 1.9 #193

build(deps): bump tgymnich/fork-sync from 1.8 to 1.9

6f2dd1e
Select commit
Loading
Failed to load commit list.
Closed

build(deps): bump tgymnich/fork-sync from 1.8 to 1.9 #193

build(deps): bump tgymnich/fork-sync from 1.8 to 1.9
6f2dd1e
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 4, 2024 in 3s

7 rules match and 23 potential rules

Rule: Add merge train label (comment, label)

  • queue-position >= 0

✅ Rule: Remove merge train label (label)

  • queue-position = -1

Rule: Ask to resolve conflict (comment, label)

  • conflict

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

  • -conflict

Rule: Notify author when added to merge queue (comment)

  • check-pending=Queue: Embarked in merge train

Rule: Notify author on queue failure (comment)

  • check-failure=Queue: Embarked in merge train

Rule: Add A-cannon label (label)

  • files~=^cannon/

Rule: Add A-indexer label and ecopod reviewers (label, request_reviews)

  • #label<5
  • files~=^indexer/

✅ Rule: Add A-op-batcher label (label)

  • files~=^op-batcher/

Rule: Add A-op-bindings label (label)

  • files~=^op-bindings/

Rule: Add A-op-bootnode label (label)

  • #label<5
  • files~=^op-bootnode/

Rule: Add A-op-chain-ops label (label)

  • files~=^op-chain-ops/

Rule: Add A-op-challenger label (label)

  • files~=^op-challenger/

Rule: Add A-op-e2e label (label)

  • #label<5
  • files~=^op-e2e/

Rule: Add A-op-heartbeat label (label)

  • #label<5
  • files~=^op-heartbeat/

✅ Rule: Add A-op-node label (label)

  • files~=^op-node/

Rule: Add A-op-preimage label (label)

  • #label<5
  • files~=^op-preimage/

✅ Rule: Add A-op-program label (label)

  • files~=^op-program/

✅ Rule: Add A-op-proposer label (label)

  • files~=^op-proposer/

Rule: Add A-op-service label (label)

  • #label<5
  • files~=^op-service/

Rule: Add A-op-wheel label (label)

  • #label<5
  • files~=^op-wheel/

Rule: Add A-ops-bedrock label (label)

  • #label<5
  • files~=^ops-bedrock/

Rule: Add A-ops label (label)

  • #label<5
  • files~=^ops/

Rule: Add A-pkg-chain-mon label (label)

  • #label<5
  • files~=^packages/chain-mon/

✅ Rule: Add A-pkg-contracts-bedrock label (label)

  • files~=^packages/contracts-bedrock/

Rule: Add A-pkg-sdk label and ecopod reviewers (label, request_reviews)

  • #label<5
  • files~=^packages/sdk/

Rule: Add A-proxyd label (label)

  • #label<5
  • files~=^proxyd/

Rule: Add M-docs label (label)

  • #label<5
  • files~=^(docs|specs)\/

Rule: Add M-deletion label when files are removed (label)

  • removed-files~=^/

Rule: Add M-ci label when ci files are modified (label)

  • #label<5
  • files~=^\.(github|circleci|husky)\/

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

🚀  You can help us by becoming a sponsor!


1 not applicable rule

Rule: Automatic merge on approval (queue)

  • all of:
    • #approved-reviews-by>=1
    • base=develop
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved=0
    • label!=M-do-not-merge
    • label!=M-mergify-ignore
    • label!=M-multiple-reviewers
    • label!=do-not-merge
    • label!=mergify-ignore
    • label!=multiple-reviewers
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • author!=dependabot[bot]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • label!=C-urgent
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
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