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

No inlining let-bound global vars with clock types #2846

Merged
merged 1 commit into from
Dec 3, 2024

Merge pull request #2844 from clash-lang/fix_2839

6f9b730
Select commit
Loading
Failed to load commit list.
Merged

No inlining let-bound global vars with clock types #2846

Merge pull request #2844 from clash-lang/fix_2839
6f9b730
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 3, 2024 in 2s

1 rule matches and 5 potential rules

⚠️ The pull request has been merged by @christiaanb

‼️ Action Required ‼️

The configuration uses the deprecated update_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: backport patches to 1.2 (copy)

  • label=backport 1.2
  • base=master
  • merged

Rule: backport patches to 1.4 (copy)

  • label=backport 1.4
  • base=master
  • merged

Rule: backport patches to 1.6 (queue)

  • -closed [📌 queue requirement]
  • label=backport 1.6
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=master
  • merged
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = ci/gitlab/gitlab.com
        • check-neutral = ci/gitlab/gitlab.com
        • check-skipped = ci/gitlab/gitlab.com
      • any of: [🛡 GitHub branch protection]
        • check-success = All jobs finished
        • check-neutral = All jobs finished
        • check-skipped = All jobs finished

Rule: backport patches to 1.6 (copy)

  • label=backport 1.6
  • base=master
  • merged

Rule: backport patches to 1.8 (queue)

  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=master
  • label=backport 1.8
  • merged
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = ci/gitlab/gitlab.com
        • check-neutral = ci/gitlab/gitlab.com
        • check-skipped = ci/gitlab/gitlab.com
      • any of: [🛡 GitHub branch protection]
        • check-success = All jobs finished
        • check-neutral = All jobs finished
        • check-skipped = All jobs finished

✅ Rule: backport patches to 1.8 (copy)

  • base=master
  • label=backport 1.8
  • merged

💖  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