docs: rename changelog workflow input to "Branch to release"#6215
Merged
Conversation
The 'Update changelog' workflow input key is already 'branch' and is used semantically as a git branch throughout (checkout ref, PR base, and generated branch name). Update the human-facing description from 'Version to release' to 'Branch to release' to match.
olehermanse
approved these changes
Jul 2, 2026
SimonThalvorsen
approved these changes
Jul 2, 2026
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
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.
Requested by Ole Herman · Slack thread
Before / After
The
workflow_dispatchinput in.github/workflows/update-changelog.ymlwas labeled "Version to release (3.24.x, 3.27.x, master)", even though the value it accepts is a git branch and the workflow uses it exactly that way (as the checkoutref, the pull-requestbase, and part of the generated branch name).After this change the input is labeled "Branch to release (3.24.x, 3.27.x, master)", which accurately describes what the field is. The input key was already
branch, so no code references needed to change.How
Single-line edit to the
inputs.branch.descriptionstring in.github/workflows/update-changelog.yml. No behavioral change — this is a display-text-only update.Note for reviewers
The task also asked to ensure the
create-pull-requestaction is pinned to@v7. It already is, but the workflow uses thecfengine/create-pull-requestfork rather than upstreampeter-evans/create-pull-request. I left the org as-is since switching to upstream could be an unintended behavioral change (the fork may exist deliberately). Flagging for a human to confirm whether a switch topeter-evans/create-pull-request@v7is actually wanted.Generated by Claude Code