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.

Sign up for GitHub

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

Modify windows-build.yml to use ffmpeg 7.0 #839

Merged
merged 1 commit into from
May 11, 2024

Modify windows-build.yml to use ffmpeg 7.0

fc216bf
Select commit
Loading
Failed to load commit list.
Merged

Modify windows-build.yml to use ffmpeg 7.0 #839

Modify windows-build.yml to use ffmpeg 7.0
fc216bf
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 11, 2024 in 0s

1 potential rule

⚠️ The pull request has been merged by @shssoichiro

Rule: automatic squash-merge for master when CI passes and approved (queue)

  • all of:
    • check-success=SonarCloud Code Analysis
    • check-success=all-tests
    • check-success=docker
  • #approved-reviews-by>=1
  • -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]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=all-tests
        • check-neutral=all-tests
        • check-skipped=all-tests
      • any of: [🛡 GitHub branch protection]
        • check-success=docker
        • check-neutral=docker
        • check-skipped=docker
💖  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 for stable when CI passes and approved (queue)

  • base=stable
  • all of:
    • check-success=SonarCloud Code Analysis
    • check-success=all-tests
    • check-success=docker
  • #approved-reviews-by>=1
  • -draft [📌 queue requirement]
  • 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 branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=all-tests
        • check-neutral=all-tests
        • check-skipped=all-tests
      • any of: [🛡 GitHub branch protection]
        • check-success=docker
        • check-neutral=docker
        • check-skipped=docker
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

View more details on Mergify