Skip to content

Conversation

@samueltardieu
Copy link
Member

This is a newly added triagebot capability, which allows registering and then resolving concerns with an issue or a pull request. The concerns are gathered by Triagebot in the issue/PR summary.

Concerns are different from notes: when a concern is resolved, it is striked through in the issue/PR summary, and a link to the comment resolving it is also added, whereas a note can only be removed and then disappears from the summary.

The has-concerns label, which must be created at the time of merging this change, will be automatically set on issues/PRs that have unresolved concerns, and cleared when all concerns are resolved.

changelog: none

@rustbot
Copy link
Collaborator

rustbot commented May 29, 2025

r? @flip1995

rustbot has assigned @flip1995.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label May 29, 2025
@samueltardieu
Copy link
Member Author

@samueltardieu
Copy link
Member Author

Ping @flip1995

Copy link
Member

@flip1995 flip1995 left a comment

Choose a reason for hiding this comment

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

Oh, that fell under my radar twice. Sorry!

@flip1995 flip1995 added this pull request to the merge queue Jul 2, 2025
@flip1995 flip1995 removed this pull request from the merge queue due to a manual request Jul 2, 2025
@flip1995
Copy link
Member

flip1995 commented Jul 2, 2025

Wait, before merging: Should the label be S-has-concerns? It's kinda a status label, isn't it?

rust-lang/rust uses S-waiting-on-concerns. I propose we use the same one, I'll update the PR. Good catch.

This is a newly added triagebot capability, which allows registering and
then resolving concerns with an issue or a pull request. The concerns
are gathered by Triagebot in the issue/PR summary.

Concerns are different from notes: when a concern is resolved, it is
striked through in the issue/PR summary, and a link to the comment
resolving it is also added, whereas a note can only be removed and then
disappears from the summary.

The `has-concerns` label, which must be created at the time of merging
this change, will be automatically set on issues/PRs that have
unresolved concerns, and cleared when all concerns are resolved.
@flip1995 flip1995 added this pull request to the merge queue Jul 2, 2025
@flip1995
Copy link
Member

flip1995 commented Jul 2, 2025

I created the label :shipit:

Merged via the queue into rust-lang:master with commit 8b034bc Jul 2, 2025
11 checks passed
@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label Jul 2, 2025
@samueltardieu samueltardieu deleted the triagebot-concerns branch July 2, 2025 18:14
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