mergify-ci

What problem does it solve?

Manually handling Mergify CI tasks like uploading test results, detecting changed code scopes, and retrieving merge queue metadata is time-consuming and error-prone, especially when supporting multiple CI providers and edge cases like silent test failures or quarantine evaluation.

Core Features & Use Cases

• JUnit Test Result Processing: Upload JUnit XML results to Mergify CI Insights, evaluate test quarantine status, and detect silent test runner failures where the exit code is non-zero but no test failures are reported.
• Git Reference Detection: Automatically identify base and head git references for pull requests across GitHub Actions, Buildkite, CircleCI, and Jenkins to power diff-based operations like affected project testing.
• CI Scope Management: Detect impacted test scopes from file changes to run targeted CI jobs instead of full test suites, reducing pipeline runtime.
• Merge Queue Metadata Retrieval: Get batch context for merge queue pull requests to adjust CI workflows based on queue position and batch composition. A common use case is a software engineering team configuring PR CI pipelines: they can use this skill to automate test result processing, run only relevant tests for changed scopes, and pull merge queue context without writing custom scripts for each CI provider.

Quick Start

Use the mergify-ci skill to process your JUnit test results, detect impacted CI scopes, and retrieve merge queue metadata for your current pull request.