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

update the workflows to test the artifacts and docker images on arm64 runners #3854

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

update the workflows to test the artifacts and docker images on arm64…

041fbba
Select commit
Loading
Failed to load commit list.
Draft

update the workflows to test the artifacts and docker images on arm64 runners #3854

update the workflows to test the artifacts and docker images on arm64…
041fbba
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 20, 2024 in 2s

1 potential rule

Rule: Thank contributor (comment)

  • merged
  • -author~=^dependabot(|-preview)\[bot\]$

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

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: Automatic approve on dependabot PR (review)

  • author~=^dependabot(|-preview)\[bot\]$

Rule: Automatic merge on dependabot PR after success CI (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #commits-behind=0
  • -draft [📌 merge requirement]
  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=DotNet Format
  • check-success=Release
  • any of: [🛡 GitHub branch protection]
    • check-neutral = CodeQL
    • check-skipped = CodeQL
    • check-success = CodeQL
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Build & Package / windows-latest
    • check-skipped = Build & Package / windows-latest
    • check-success = Build & Package / windows-latest
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Build & Package / ubuntu-latest
    • check-skipped = Build & Package / ubuntu-latest
    • check-success = Build & Package / ubuntu-latest
  • any of: [🛡 GitHub branch protection]
    • check-neutral = DotNet Format
    • check-skipped = DotNet Format
    • check-success = DotNet Format
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Test / ubuntu-latest - net8.0
    • check-skipped = Test / ubuntu-latest - net8.0
    • check-success = Test / ubuntu-latest - net8.0
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Test / windows-latest - net8.0
    • check-skipped = Test / windows-latest - net8.0
    • check-success = Test / windows-latest - net8.0
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Release
    • check-skipped = Release
    • check-success = Release
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Test / macos-15 - net8.0
    • check-skipped = Test / macos-15 - net8.0
    • check-success = Test / macos-15 - net8.0
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Build & Package / macos-15
    • check-skipped = Build & Package / macos-15
    • check-success = Build & Package / macos-15
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • repository-full-name=GitTools/GitVersion
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
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