Avoid backlink noise when notifying PRs of uv.lock conflicts - #71001
Merged
Conversation
eladkal
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
August 3, 2026 15:53
potiuk
approved these changes
Aug 3, 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
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 uv.lock conflict notifier (scripts/ci/notify_uv_lock_conflicts.py)
posts a comment on conflicting PRs linking back to the PR/commit that
bumped uv.lock on main. Because GitHub auto-generates a backlink
comment on any issue/PR referenced this way, every notification also
produced an unwanted comment on the original PR — noise unrelated to
its own discussion.
GitHub's docs describe using the redirect.github.com host instead of
github.com to suppress this automatic backlink behavior:
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#avoiding-backlinks-to-linked-references
This adds an
avoid_backlink()helper and applies it to both linksembedded in the notice body (the source PR link and the commit link).
The plain-text log/summary output is left untouched since it's never
posted to GitHub.
without this change we are getting too many useless refrences:
Was generative AI tooling used to co-author this PR?
Generated-by: Claude (Sonnet 4.5) following the guidelines