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

Mappers #352

Merged
merged 4 commits into from
Nov 11, 2024

feat: jalecoss88006

406777a
Select commit
Loading
Failed to load commit list.
Merged

Mappers #352

feat: jalecoss88006
406777a
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 11, 2024 in 1s

1 potential rule

⚠️ The pull request has been merged by @lukexor

Rule: Update PRs to latest main (update)

  • #commits-behind > 0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -author=dependabot[bot]
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • -head~=release-plz-*
  • queue-position = -1 [📌 update requirement]

💖  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: Merge Dependabot PRs (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • author=dependabot[bot]
  • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Lint Web
    • check-skipped = Lint Web
    • check-success = Lint Web
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Security Audit
    • check-skipped = Security Audit
    • check-success = Security Audit
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Check format
    • check-neutral = Check format
    • check-skipped = Check format
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES (ubuntu-latest)
    • check-neutral = Lint TetaNES (ubuntu-latest)
    • check-skipped = Lint TetaNES (ubuntu-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES (windows-latest)
    • check-neutral = Lint TetaNES (windows-latest)
    • check-skipped = Lint TetaNES (windows-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES (macos-latest)
    • check-neutral = Lint TetaNES (macos-latest)
    • check-skipped = Lint TetaNES (macos-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES Core (macos-latest)
    • check-neutral = Lint TetaNES Core (macos-latest)
    • check-skipped = Lint TetaNES Core (macos-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES Core (ubuntu-latest)
    • check-neutral = Lint TetaNES Core (ubuntu-latest)
    • check-skipped = Lint TetaNES Core (ubuntu-latest)
  • any of: [🛡 GitHub branch protection]
    • check-success = Lint TetaNES Core (windows-latest)
    • check-neutral = Lint TetaNES Core (windows-latest)
    • check-skipped = Lint TetaNES Core (windows-latest)
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