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

feat: additional options when assuming publishing roles #40

Merged
merged 34 commits into from
Sep 19, 2024

Merge branch 'v2-main' into sumughan/add-session-tags-to-client-options

b406ba1
Select commit
Loading
Failed to load commit list.
Merged

feat: additional options when assuming publishing roles #40

Merge branch 'v2-main' into sumughan/add-session-tags-to-client-options
b406ba1
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 19, 2024 in 1s

1 rule matches and 1 potential rule

‼️ Action Required ‼️

The configuration uses the deprecated commit_message_template 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 September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ 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 September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

✅ Rule: Automatic merge on approval and successful build (delete_head_branch)

  • #approved-reviews-by>=1
  • -label~=(do-not-merge)
  • closed [📌 delete_head_branch requirement]
  • status-success=build

Rule: Automatic merge on approval and successful build (queue)

  • -closed [📌 queue requirement]
  • #approved-reviews-by>=1
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=(do-not-merge)
  • status-success=build
  • 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 repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • branch-protection-review-decision = APPROVED [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub repository ruleset rule]
        • check-success = build
        • check-neutral = build
        • check-skipped = build
      • any of: [🛡 GitHub repository ruleset rule]
        • check-success = Validate PR title
        • check-neutral = Validate PR title
        • check-skipped = Validate PR title

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

🚀  You can help us by becoming a sponsor!


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