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

chore(deps): bump Uno.WinUI.WebAssembly from 5.0.0-dev.3552 to 5.0.48 #148

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

chore(deps): bump Uno.WinUI.WebAssembly from 5.0.0-dev.3552 to 5.0.48

5c8b8da
Select commit
Loading
Failed to load commit list.
Open

chore(deps): bump Uno.WinUI.WebAssembly from 5.0.0-dev.3552 to 5.0.48 #148

chore(deps): bump Uno.WinUI.WebAssembly from 5.0.0-dev.3552 to 5.0.48
5c8b8da
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 3, 2024 in 1s

no rules match, no planned actions


💖  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 merge for allcontributors pull requests (merge)

  • author=allcontributors[bot]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=build
    • check-neutral=build
    • check-skipped=build

Rule: automatic strict merge when CI passes, has 2 reviews, no requests for change and is labeled 'ready-to-merge' unless labelled 'do-not-merge/breaking-change' or 'do-not-merge/work-in-progress' (merge)

  • #approved-reviews-by>=2
  • base=master
  • label!=do-not-merge/work-in-progress
  • label=ready-to-merge
  • status-success=Uno.UI - CI
  • #changes-requested-reviews-by=0
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • label!=do-not-merge/breaking-change
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=build
    • check-neutral=build
    • check-skipped=build
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