Skip to content

Comments

Enable [range-diff], [transfer] and [view-all-comments-link] org-wide#2300

Open
Urgau wants to merge 1 commit intorust-lang:masterfrom
Urgau:org-wide-range-diff-view-all-comment-transfer
Open

Enable [range-diff], [transfer] and [view-all-comments-link] org-wide#2300
Urgau wants to merge 1 commit intorust-lang:masterfrom
Urgau:org-wide-range-diff-view-all-comment-transfer

Conversation

@Urgau
Copy link
Member

@Urgau Urgau commented Feb 23, 2026

Following #2294, let's enable three more handlers org-wide:

  • [range-diff]: adds a link to show a range-diff when a PR is rebased onto a different base commit
  • [transfer]: enables issue transfers within the org
  • [view-all-comments-link]: adds a "View all comments" link on the issue/PR body that shows all the comments of it

cc @Mark-Simulacrum @jieyouxu

@Urgau Urgau requested a review from Kobzol February 23, 2026 20:05
Copy link
Member

@Kobzol Kobzol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

View all comments and transfer seems harmless enough. Range diff might be a bit too chatty on some repos, but we'll see what happens.

View changes since this review

@Urgau
Copy link
Member Author

Urgau commented Feb 23, 2026

I'm thinking about this for the announcement:


Next up, we’re turning on three more triagebot features across all triagebot-enabled rust-lang repositories:

  • [range-diff] – adds a link to show what changed when a PR gets rebased
  • [transfer] – enables @rustbot transfer to move issues between repos in the org
  • [view-all-comments-link] – adds a "View all comments" link to see the full GitHub conversation in one place

As before, any repository can opt out if needed.

@Mark-Simulacrum
Copy link
Member

[view-all-comments-link] – adds a "View all comments" link to see the full GitHub conversation in one place

Does this end up in PR merges for GitHub-owned merges (e.g., merge queues)? Can we avoid that? cc #2302

Maybe not a hard blocker but could be worth waiting a little more there. Maybe we can recommend folks setup a bookmarklet that redirects for that instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants