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

Migration: Add Market ID to Market #1257

Merged
merged 17 commits into from
Apr 9, 2024

Remove unused `types/`

2b82ed2
Select commit
Loading
Failed to load commit list.
Merged

Migration: Add Market ID to Market #1257

Remove unused `types/`
2b82ed2
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Apr 9, 2024 in 0s

2 rules match and 4 potential rules

✅ Rule: Auto merge (feature branch) (queue)

  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -draft [📌 queue requirement]
  • base!=main
  • check-success=Checks (clippy)
  • check-success=Checks (parachain)
  • check-success=Checks (standalone)
  • check-success=Coverage
  • check-success=Format
  • check-success=Fuzz
  • check-success=Quick check benchmarks
  • check-success=Test parachain build
  • check-success=Test standalone build
  • label=s:accepted
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

✅ Rule: Auto merge (feature branch) (label)

  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • base!=main
  • check-success=Checks (clippy)
  • check-success=Checks (parachain)
  • check-success=Checks (standalone)
  • check-success=Coverage
  • check-success=Format
  • check-success=Fuzz
  • check-success=Quick check benchmarks
  • check-success=Test parachain build
  • check-success=Test standalone build
  • label=s:accepted

Rule: ask to resolve conflict (comment, label)

  • conflict

Rule: Set in-progress label after changes are pushed (label)

  • commits[-1].date_committer>=0 days 00:01 ago
  • commits[-1].author!=mergify[bot]

Rule: Trigger CI after Mergify merged the base branch (fix merge queue) (label)

  • commits[-1].author=mergify[bot]
  • commits[-1].date_committer>=0 days 00:01 ago
  • queue-position=0

Rule: Remove CI trigger label (label)

  • commits[-1].author=mergify[bot]
  • label=s:review-needed
  • queue-position=0

💖  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: Auto merge (main) (queue)

  • base=main
  • check-success=Copyright Notices
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • -draft [📌 queue requirement]
  • check-success=Checks (clippy)
  • check-success=Checks (parachain)
  • check-success=Checks (standalone)
  • check-success=Coverage
  • check-success=Format
  • check-success=Fuzz
  • check-success=Quick check benchmarks
  • check-success=Test parachain build
  • check-success=Test standalone build
  • label=s:accepted
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

Rule: Auto merge (main) (label)

  • base=main
  • check-success=Copyright Notices
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • check-success=Checks (clippy)
  • check-success=Checks (parachain)
  • check-success=Checks (standalone)
  • check-success=Coverage
  • check-success=Format
  • check-success=Fuzz
  • check-success=Quick check benchmarks
  • check-success=Test parachain build
  • check-success=Test standalone build
  • label=s:accepted
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