Skip to content

Conversation

@apiraino
Copy link
Contributor

@apiraino apiraino commented Oct 2, 2025

Beta backport nominations were confusing so we decided to turn them into suggestions for reviewers and author of a PR fixing a regression. The idea is to raise awareness on patches fixing P-high/P-critical regressions but at the same time not make it look like a mandatory decision for T-compiler to take.

After this patch, I will modify the template that creates Zulip topics for backport nominations. For example it could look like this:

PR #123456 "Fix insulation in flux capacitor" fixes a regression. Cc: @user1, @user2, @user3 please evaluate nominating this PR for backport, thanks! The following poll is a vibe-check and not binding. /poll Should #123456 be beta backported? approve decline don't know 
(visual representation)

grafik

(@user1, @user2, @user3) are PR author and reviewers.

As per Zulip discussion.

@apiraino apiraino force-pushed the change-backport-nominations branch from f4c2231 to c347fd8 Compare October 6, 2025 15:27
Comment on lines +220 to +223
// Issue/PR authors/reviewers will receive a mention if the template has `{recipients}`.
let recipients = &mut event.issue.assignees.clone();
recipients.push(event.issue.user.clone());

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is different from before: if the template has a {recipients} placeholder, author and reviewers of the PR/issue will receive a mention.

(this change is very specific to my use-case but I think it can be used in other contexts)

Ok(())
}

async fn get_zulip_ids(ctx: &Context, recipients: &[User]) -> String {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this code here is duplicating what we have in src/zulip.rs so a better way would be to refactor that module and expose functions. Maybe another time.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

to generate the mention it's using the trick to write @|12345 where 12345 is the Zulip ID of the user.

@apiraino apiraino marked this pull request as ready for review October 6, 2025 15:51
@Kobzol
Copy link
Member

Kobzol commented Oct 7, 2025

Let me know if you want a review.

@apiraino apiraino requested a review from Kobzol October 7, 2025 07:17
@apiraino apiraino force-pushed the change-backport-nominations branch from c347fd8 to 63ae02e Compare October 7, 2025 16:01
@apiraino apiraino requested a review from Kobzol October 7, 2025 16:14
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.

Thanks, let's try.

View changes since this review

@Kobzol Kobzol added this pull request to the merge queue Oct 7, 2025
Merged via the queue into rust-lang:master with commit d16ca50 Oct 7, 2025
3 checks passed
@apiraino apiraino deleted the change-backport-nominations branch October 7, 2025 18:44
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 15, 2025
…, r=Kobzol Update t-compiler beta nomination Zulip msg Sister patch of [triagebot#2191](rust-lang/triagebot#2191) Follow-up to rust-lang#147263 The triagebot now triggers a different message when a PR is nominated for backport, making it look like more a suggestion to evaluate for the author/reviewers than a mandatory decision for the team to take. The wording (as per [triagebot#2191](rust-lang/triagebot#2191)) is open to suggestions. Thanks
rust-timer added a commit to rust-lang/rust that referenced this pull request Oct 16, 2025
Rollup merge of #147527 - apiraino:update-beta-nom-zulip-msg, r=Kobzol Update t-compiler beta nomination Zulip msg Sister patch of [triagebot#2191](rust-lang/triagebot#2191) Follow-up to #147263 The triagebot now triggers a different message when a PR is nominated for backport, making it look like more a suggestion to evaluate for the author/reviewers than a mandatory decision for the team to take. The wording (as per [triagebot#2191](rust-lang/triagebot#2191)) is open to suggestions. Thanks
github-actions bot pushed a commit to rust-lang/miri that referenced this pull request Oct 16, 2025
Update t-compiler beta nomination Zulip msg Sister patch of [triagebot#2191](rust-lang/triagebot#2191) Follow-up to rust-lang/rust#147263 The triagebot now triggers a different message when a PR is nominated for backport, making it look like more a suggestion to evaluate for the author/reviewers than a mandatory decision for the team to take. The wording (as per [triagebot#2191](rust-lang/triagebot#2191)) is open to suggestions. Thanks
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Oct 18, 2025
Update t-compiler beta nomination Zulip msg Sister patch of [triagebot#2191](rust-lang/triagebot#2191) Follow-up to rust-lang/rust#147263 The triagebot now triggers a different message when a PR is nominated for backport, making it look like more a suggestion to evaluate for the author/reviewers than a mandatory decision for the team to take. The wording (as per [triagebot#2191](rust-lang/triagebot#2191)) is open to suggestions. Thanks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants