docs(ci-insights): documents the gha-mergify-ci job_name input for matrix job naming - #13039
Merged
mergify[bot] merged 1 commit intoSep 28, 2026
Conversation
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Sep 28, 2026
Contributor
Merge Queue Status
This pull request spent 3 minutes 21 seconds in the queue, including 2 minutes 59 seconds running CI. Required conditions to merge
|
49 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The page explained how to keep a scheduled run's job name aligned with the pull
request run, and offered exactly one way to do it: set
MERGIFY_TEST_JOB_NAMEin the workflow job's
env. That works, but the action used two snippetsearlier on the same page declares a
job_nameinput for precisely this case,and the Buildkite page documents its plugin equivalent — so a reader uploading
through the action was being pointed at the indirect route while the direct one
went unmentioned.
The bullet now shows the input alongside the environment variable, and says
which wins: the input takes precedence, and leaving it out keeps whatever name
the job set. Matrix builds are where this matters, because every matrix job
reports the same
GITHUB_JOBand therefore the same default name.Evidence: the action's input declaration, and the precedence it applies when
both the input and the environment variable are present.