Repository navigation
fix(linker): match issue keys case-insensitively in LinkPrToIssue - #9336
Merged
klesh merged 1 commit intoNov 8, 2026
Merged
Conversation
VictorColomb
marked this pull request as ready for review
November 6, 2026 16:11
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.
Summary
LinkPrToIssuecompared extracted keys toissues.issue_keywith an exact, case-sensitive match, so lowercase branch names likeuser/proj-123-titlenever linked toPROJ-123(on case-sensitive DBs such as PostgreSQL).Does this close any open issues?
Closes #9283
Other Information
Added e2e test
TestLinkPrToIssueCaseInsensitive. It fails without the fix on PostgreSQL; on MySQL the default collation is already case-insensitive, so it passes either way.