Repository navigation
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.
Refactor shared value formatting and unify GitHub error/SHA classification paths #53018
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Refactor shared value formatting and unify GitHub error/SHA classification paths #53018
Changes from 1 commit
3bb758bd07bf7c3ef7e0da0856f249a8e93aaec1b17935c8f6f6c0ecFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/codebase-design]
marshalEnvValuenow silently returns""whenFormatResolvedValuereturns(_, false)andv == nilis false — i.e. it falls through tofmt.Sprint(v). ButFormatResolvedValuereturnsfalseonly fornil; all other types returntrue. The double-nil guard (if s, ok := ...; okthenif v == nil) therefore creates a dead-code branch: the secondif v == nilis unreachable becauseFormatResolvedValue(nil)returns("", false)so the first branch doesn't return, but thenv == nilis true.This means
nilreturns""correctly, but the structure is confusing — a futureFormatResolvedValuechange that returnsfalsefor non-nil values (e.g. a marshalling error) would silently fall intofmt.Sprint.💡 Suggested fix
Either log/surface the marshalling failure, or be explicit:
This makes the
nilguard first-class and the fallback readable.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved the nil guard before
FormatResolvedValuein aaec1b1.Uh oh!
There was an error while loading. Please reload this page.