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

fix(charts): update helm release loki to v5.43.5 - autoclosed #2641

Merged
merged 1 commit into from
Mar 6, 2024

fix(charts): update helm release loki to v5.43.5

812b189
Select commit
Loading
Failed to load commit list.
Merged

fix(charts): update helm release loki to v5.43.5 - autoclosed #2641

fix(charts): update helm release loki to v5.43.5
812b189
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 6, 2024 in 0s

1 potential rule

⚠️ The pull request has been merged by @ArchiFleKs

Rule: Automatic merge on approval (merge)

  • -closed [πŸ“Œ merge requirement]
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral=Max TF pre-commit
    • check-skipped=Max TF pre-commit
    • check-success=Max TF pre-commit
  • #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

πŸ’–Β Β 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
  • any of: [πŸ›‘ GitHub branch protection]
    • check-neutral=Max TF pre-commit
    • check-skipped=Max TF pre-commit
    • check-success=Max TF pre-commit
  • #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
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