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

Add support for “known failures” to transcripts #5394

Open
wants to merge 4 commits into
base: trunk
Choose a base branch
from

Add first `:incorrect` transcript

56a2f5c
Select commit
Loading
Failed to load commit list.
Open

Add support for “known failures” to transcripts #5394

Add first `:incorrect` transcript
56a2f5c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 7, 2024 in 1s

2 potential rules

Rule: automatic merge on CI success and review (merge)

  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • label=ready-to-merge
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=build jit binary / build jit binary (macOS-12)
  • check-success=build jit binary / build jit binary (ubuntu-20.04)
  • check-success=build jit binary / build jit binary (windows-2019)
  • check-success=build ucm (macOS-12)
  • check-success=build ucm (ubuntu-20.04)
  • check-success=build ucm (windows-2019)
  • check-success=check-contributor
  • check-success=generate jit source
  • check-success=run interpreter tests (macOS-12)
  • check-success=run interpreter tests (ubuntu-20.04)
  • check-success=run transcripts (macOS-12)
  • check-success=run transcripts (ubuntu-20.04)
  • check-success=run transcripts (windows-2019)
  • check-success=test jit / test jit (macOS-12)
  • check-success=test jit / test jit (ubuntu-20.04)
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = Summary
    • check-neutral = Summary
    • check-skipped = Summary

Rule: automatic merge on CI success and review (label)

  • #approved-reviews-by>=1
  • label=ready-to-merge
  • check-success=build jit binary / build jit binary (macOS-12)
  • check-success=build jit binary / build jit binary (ubuntu-20.04)
  • check-success=build jit binary / build jit binary (windows-2019)
  • check-success=build ucm (macOS-12)
  • check-success=build ucm (ubuntu-20.04)
  • check-success=build ucm (windows-2019)
  • check-success=check-contributor
  • check-success=generate jit source
  • check-success=run interpreter tests (macOS-12)
  • check-success=run interpreter tests (ubuntu-20.04)
  • check-success=run transcripts (macOS-12)
  • check-success=run transcripts (ubuntu-20.04)
  • check-success=run transcripts (windows-2019)
  • check-success=test jit / test jit (macOS-12)
  • check-success=test jit / test jit (ubuntu-20.04)

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

🚀  You can help us by becoming a sponsor!


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