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

Jump to bottom

fix: Report more detailed exception on parsing errors #23

Merged
merged 1 commit into from
Nov 5, 2024

fix: Report more detailed exception on parsing errors

daaee68
Select commit
Loading
Failed to load commit list.
Merged

fix: Report more detailed exception on parsing errors #23

fix: Report more detailed exception on parsing errors
daaee68
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 5, 2024 in 2s

no rules match, no planned actions

⚠️ The pull request has been merged by @jeromelaban

💖  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)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • author=allcontributors[bot]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • -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 Extensions
    • check-neutral = Build Extensions
    • check-skipped = Build Extensions
  • any of: [🛡 GitHub branch protection]
    • check-success = Build Tools
    • check-neutral = Build Tools
    • check-skipped = Build Tools

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 >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=2
  • -closed [📌 merge requirement]
  • base=master
  • label=ready-to-merge
  • status-success=Uno.UI - CI
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • 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-success = Build Extensions
    • check-neutral = Build Extensions
    • check-skipped = Build Extensions
  • any of: [🛡 GitHub branch protection]
    • check-success = Build Tools
    • check-neutral = Build Tools
    • check-skipped = Build Tools
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