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

docs: how to backport ncap to an existing golang-crossbuild version #321

Merged
merged 1 commit into from
Sep 28, 2023

docs: how to backport ncap to an existing golang-crossbuild versoin

c3805bc
Select commit
Loading
Failed to load commit list.
Merged

docs: how to backport ncap to an existing golang-crossbuild version #321

docs: how to backport ncap to an existing golang-crossbuild versoin
c3805bc
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 28, 2023 in 2s

8 potential rules

⚠️ The pull request has been merged by @v1v

Rule: ask to resolve conflict (comment)

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

Rule: notify the backport policy (comment, label)

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

Rule: remove-backport label (label)

  • -closed
  • -merged
  • label~=backport-v

Rule: backport patches to 1.16 branch (backport)

  • label=backport-v1.16
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 1.17 branch (backport)

  • label=backport-v1.17
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 1.18 branch (backport)

  • label=backport-v1.18
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 1.19 branch (backport)

  • label=backport-v1.19
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 1.20 branch (backport)

  • label=backport-v1.20
  • merged
  • merged [:pushpin: backport requirement]

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


5 not applicable rules

Rule: delete upstream branch after merging changes on Jenkinsfile or it's closed (delete_head_branch)

  • all of:
    • files~=^Jenkinsfile$
    • head~=^updatecli
    • label=automation
  • closed [:pushpin: delete_head_branch requirement]
  • any of:
    • closed
    • merged

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

  • author=apmmachine
  • files~=^go/Makefile.common
  • label=automation
  • check-success=beats-ci/pr-merge

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

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

Rule: squash and merge updatecli PRs after CI passes with golang bump updates (queue)

  • files~=^go/Makefile.common
  • head~=^updatecli
  • label=automation
  • -conflict
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=beats-ci/pr-merge
        • check-neutral=beats-ci/pr-merge
        • check-skipped=beats-ci/pr-merge
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA

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

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