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

docs: Add Binding to DataTemplates docs #2292

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

chore: Resolving csm binding docs comments

6d8d111
Select commit
Loading
Failed to load commit list.
Draft

docs: Add Binding to DataTemplates docs #2292

chore: Resolving csm binding docs comments
6d8d111
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 12, 2025 in 3s

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)

  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • -draft [📌 merge requirement]
  • author=allcontributors[bot]
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-neutral = uno.extensions
    • check-skipped = uno.extensions
    • check-success = uno.extensions
  • any of: [🛡 GitHub branch protection]
    • check-success = Validate for conventional commits
    • check-neutral = Validate for conventional commits
    • check-skipped = Validate for conventional commits

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)

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