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

[CI] Update label in schedule daily job definition as part of the automation #10722

Merged
merged 12 commits into from
Aug 9, 2024

Remove empty line

10a8455
Select commit
Loading
Failed to load commit list.
Merged

[CI] Update label in schedule daily job definition as part of the automation #10722

Remove empty line
10a8455
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 9, 2024 in 0s

no rules match, no planned actions

⚠️ The pull request has been merged by @mrodm

‼️ 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

<hr />

💖  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 of bot 🤖 (queue)

  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=integrations/pr-merge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=buildkite/integrations
        • check-skipped=buildkite/integrations
        • check-success=buildkite/integrations
      • #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
  • -draft [📌 queue requirement]
  • base=main
  • check-success=CLA
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
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