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.

Sign up for GitHub

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

Jump to bottom

feat(tf): update terraform jinja to v2 #2598

Merged
merged 1 commit into from
Feb 24, 2024

feat(tf): update terraform jinja to v2

f42802b
Select commit
Loading
Failed to load commit list.
Merged

feat(tf): update terraform jinja to v2 #2598

feat(tf): update terraform jinja to v2
f42802b
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 24, 2024 in 1s

1 potential rule

⚠️ The pull request has been merged by @ArchiFleKs

Rule: Automatic merge on approval (merge)

  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • approved-reviews-by>=1
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Max TF pre-commit
    • check-skipped=Max TF pre-commit
    • check-success=Max TF pre-commit
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #commits-behind=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=WIP
    • check-neutral=WIP
    • check-skipped=WIP
  • any of: [🛡 GitHub branch protection]
    • check-success=renovate:config
    • check-neutral=renovate:config
    • check-skipped=renovate:config
  • any of: [🛡 GitHub branch protection]
    • check-success=Summary
    • check-neutral=Summary
    • check-skipped=Summary
💖  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 release (merge)

  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • approved-reviews-by>=1
  • base=release
  • any of: [🛡 GitHub branch protection]
    • check-neutral=Max TF pre-commit
    • check-skipped=Max TF pre-commit
    • check-success=Max TF pre-commit
  • #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=WIP
    • check-neutral=WIP
    • check-skipped=WIP
  • any of: [🛡 GitHub branch protection]
    • check-success=renovate:config
    • check-neutral=renovate:config
    • check-skipped=renovate:config
  • any of: [🛡 GitHub branch protection]
    • check-success=Summary
    • check-neutral=Summary
    • check-skipped=Summary
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

View more details on Mergify