docs(ci-insights): Document glob support in mergify ci junit-process#11246
Conversation
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
1d10a09 to
6398cc2
Compare
Revision history
|
There was a problem hiding this comment.
Pull request overview
Updates CI Insights documentation to ensure glob patterns are passed to Mergify unexpanded, preventing shell-side expansion issues (notably ARG_MAX/“argument list too long”) and announces the new glob support via a changelog entry.
Changes:
- Quote the JUnit report glob in the Jenkins setup example so Mergify expands it internally.
- Add a changelog entry documenting glob pattern support for
mergify ci junit-process(and mentioningjunit-uploadas well).
Reviewed changes
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/content/docs/ci-insights/setup/jenkins.mdx | Quotes the JUnit glob in the Jenkins example and adds explanatory comments about avoiding argument-length limits. |
| src/content/changelog/2026-04-23-junit-process-supports-glob-patterns.mdx | New changelog entry announcing glob pattern support and describing why quoting avoids ARG_MAX failures. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The Jenkins setup example passed `test-results-*.xml` unquoted, so the inner shell expanded it before mergify saw it — exactly the ARG_MAX failure mode the new CLI behaviour avoids. Quote the pattern so Mergify expands it internally. Also add a changelog entry announcing the supported feature. Change-Id: I851f9acfe86e40788c84e1fd31b6db8b6db2809f References: MRGFY-7036
6398cc2 to
d27dc6c
Compare
Merge Queue Status
This pull request spent 2 minutes 51 seconds in the queue, including 2 minutes 36 seconds running CI. Waiting for any of:
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 2 minutes 20 seconds in the queue, including 1 minute 58 seconds running CI. Required conditions to merge
|
The Jenkins setup example passed
test-results-*.xmlunquoted, so theinner shell expanded it before mergify saw it — exactly the ARG_MAX
failure mode the new CLI behaviour avoids. Quote the pattern so Mergify
expands it internally.
Also add a changelog entry announcing the supported feature.
References: MRGFY-7036