Update fromBranch message for clarity on availability - #6481
#6481Merged
Merged
Update fromBranch message for clarity on availability#6481
Conversation
Right now you just get "... being divergent from the previously flown branch" which is misleading. Also fix the double-escaping when the branch name is available, we already wrap the string in backticks in the PR message.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the unsafe codeflow PR header text generation in PCS dependency flow to avoid misleading wording when the previously-flown branch isn’t known, and to prevent double-wrapping the branch value in Markdown backticks.
Changes:
- Stop pre-wrapping
fromBranchin backticks to avoid double-escaping in the rendered PR message. - Replace the generic fallback
"branch"with an explicit placeholder indicating the branch name is unavailable.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
adamzip
approved these changes
Jul 7, 2026
akoeplinger
enabled auto-merge
July 7, 2026 16:59
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.
Right now you just get "... being divergent from the previously flown
branch" which is misleading.Also fix the double-escaping when the branch name is available, we already wrap the string in backticks in the PR message.
Related issue: #6390