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(Intel CoffeeLake): Added support #1249

Merged
merged 1 commit into from
Nov 16, 2024

feat(Intel CoffeeLake): Added support

51b5f83
Select commit
Loading
Failed to load commit list.
Merged

「✨」 feat(Intel CoffeeLake): Added support #1249

feat(Intel CoffeeLake): Added support
51b5f83
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 16, 2024 in 3s

1 potential rule

⚠️ The pull request has been closed by GitHub because its commits are also part of another pull request

Rule: merge using the merge queue (queue)

  • -closed [📌 queue requirement]
  • label~=merge-queue|dependencies
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=master
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

💖  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