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

Replace github.com/coreos/go-systemd/v22/sdjournal by journalctl #40061

Merged
merged 61 commits into from
Aug 9, 2024

Fix log entry

1359a65
Select commit
Loading
Failed to load commit list.
Merged

Replace github.com/coreos/go-systemd/v22/sdjournal by journalctl #40061

Fix log entry
1359a65
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 9, 2024 in 1s

19 potential rules

⚠️ The pull request has been merged by @belimawr

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

### Rule: self-assign PRs (assign)
  • #assignee=0
  • -closed
  • -merged

Rule: forward-port patches to main branch (backport)

  • label=forwardport-main
  • merged
  • merged [📌 backport requirement]

Rule: ask to resolve conflict (comment)

  • -closed
  • -merged
  • conflict
  • -author=apmmachine

Rule: automatic squash and merge with success checks and the files matching the regex ^testing/environments/snapshot* are modified. (queue)

  • files~=^testing/environments/snapshot.*\.yml$
  • label=automation
  • #approved-reviews-by>=1
  • -draft [📌 queue requirement]
  • check-success=buildkite/beats
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #approved-reviews-by>=1 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub repository ruleset rule]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/docs-build-pr
        • check-neutral=buildkite/docs-build-pr
        • check-skipped=buildkite/docs-build-pr
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/beats
        • check-neutral=buildkite/beats
        • check-skipped=buildkite/beats

Rule: notify the backport policy (comment)

  • -closed
  • -label~=^backport
  • -merged
  • base=main

Rule: backport patches to 7.17 branch (backport)

  • label=backport-v7.17.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.3 branch (backport)

  • label=backport-v8.3.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.4 branch (backport)

  • label=backport-v8.4.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.5 branch (backport)

  • label=backport-v8.5.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.6 branch (backport)

  • label=backport-v8.6.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.7 branch (backport)

  • label=backport-v8.7.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.8 branch (backport)

  • label=backport-v8.8.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.9 branch (backport)

  • label=backport-v8.9.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.10 branch (backport)

  • label=backport-v8.10.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.11 branch (backport)

  • label=backport-v8.11.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.12 branch (backport)

  • label=backport-v8.12.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.13 branch (backport)

  • label=backport-v8.13.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.14 branch (backport)

  • label=backport-v8.14.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.15 branch (backport)

  • label=backport-v8.15.0
  • merged
  • merged [📌 backport requirement]
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

8 not applicable rules

Rule: close automated pull requests with bump updates if any conflict (close)

  • -closed
  • -merged
  • author=apmmachine
  • conflict
  • label=automation

Rule: automatic approval for automated pull requests with bump updates (review)

  • author=apmmachine
  • files~=^testing/environments/snapshot.*\.yml$
  • label=automation
  • check-success=buildkite/beats

Rule: delete upstream branch after merging changes on testing/environments/snapshot* or it's closed (delete_head_branch)

  • all of:
    • files~=^testing/environments/snapshot.*\.yml$
    • head~=^updatecli_bump-elastic-stack
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: delete upstream branch after merging changes on .go-version or it's closed (delete_head_branch)

  • all of:
    • files~=^\.go-version$
    • head~=^updatecli_bump-golang-version
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: automatic approval for mergify pull requests with changes in bump-rules (review)

  • author=mergify[bot]
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • check-success=buildkite/beats

Rule: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified. (queue)

  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • #approved-reviews-by>=1
  • -draft [📌 queue requirement]
  • check-success=buildkite/beats
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #approved-reviews-by>=1 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub repository ruleset rule]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/docs-build-pr
        • check-neutral=buildkite/docs-build-pr
        • check-skipped=buildkite/docs-build-pr
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/beats
        • check-neutral=buildkite/beats
        • check-skipped=buildkite/beats

Rule: delete upstream branch with changes on ^.mergify.yml that has been merged or closed (delete_head_branch)

  • all of:
    • files~=^\.mergify\.yml$
    • head~=^add-backport-next.*
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: notify the backport has not been merged yet (comment)

  • -closed
  • -merged
  • author=mergify[bot]
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #assignee>=1
  • #check-success>0
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