What problem does it solve? CI pipelines need to upload JUnit test results, evaluate flaky-test quarantines, detect which scopes changed, and read merge queue batch context without hand-rolled scripts against the Mergify API. ## Core Features & Use Cases - JUnit Processing: Parse JUnit XML reports, check quarantine status for failing tests, upload spans to Mergify CI Insights, and set the CI exit code so quarantined failures do not block the build. - Scopes Detection: Identify which CI scopes are impacted by changed files between base and head refs, enabling selective testing that only runs affected test suites. - Quarantine Management: Add, remove, get, and list quarantined tests, and look up test health by name with glob support. - Use Case: In a GitHub Actions workflow, run pytest with JUnit output, then call mergify ci junit-process results.xml so flaky tests already in quarantine do not fail the pipeline while real regressions still block the merge. ## Quick Start Ask the assistant to upload your JUnit test results to Mergify CI Insights and evaluate quarantine status for failing tests in your CI pipeline.
