Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix(charts): update helm release aws-efs-csi-driver to 3.1.4 (was 3.1.3) #3146

Merged
merged 1 commit into from
Dec 21, 2024

fix(charts): update helm release aws-efs-csi-driver to 3.1.4 (was 3.1.3)

2851836
Select commit
Loading
Failed to load commit list.
Merged

fix(charts): update helm release aws-efs-csi-driver to 3.1.4 (was 3.1.3) #3146

fix(charts): update helm release aws-efs-csi-driver to 3.1.4 (was 3.1.3)
2851836
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 21, 2024 in 0s

1 potential rule

Rule: Automatic merge on approval (merge)

  • -closed [πŸ“Œ merge requirement]
  • #approved-reviews-by >= 1 [πŸ›‘ GitHub branch protection]
  • #changes-requested-reviews-by = 0 [πŸ›‘ GitHub branch protection]
  • #commits-behind = 0 [πŸ›‘ GitHub branch protection]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • approved-reviews-by>=1
  • 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
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Max TF pre-commit
    • check-neutral = Max TF pre-commit
    • check-skipped = Max TF pre-commit

πŸ’–Β Β 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)

  • -closed [πŸ“Œ merge requirement]
  • base=release
  • #approved-reviews-by >= 1 [πŸ›‘ GitHub branch protection]
  • #changes-requested-reviews-by = 0 [πŸ›‘ GitHub branch protection]
  • #commits-behind = 0 [πŸ›‘ GitHub branch protection]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • approved-reviews-by>=1
  • 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
  • any of: [πŸ›‘ GitHub branch protection]
    • check-success = Max TF pre-commit
    • check-neutral = Max TF pre-commit
    • check-skipped = Max TF pre-commit
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