Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Only create a relnotes tracking issue for finished FCPs if they have disposition merge #1904

Conversation

fmease
Copy link
Member

@fmease fmease commented Feb 16, 2025

Addresses rust-lang/rust#137075 (comment)

r? @Mark-Simulacrum || (release ∩ infra)

@@ -27,6 +27,8 @@ struct RelnotesState {
relnotes_issue: Option<u64>,
}

const TITLE_PREFIX: &str = "Tracking issue for release notes";
Copy link
Member Author

Choose a reason for hiding this comment

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

Drive-by refactoring to ensure that the two usage sites don't get out of sync.

&& e.issue
.labels
.iter()
.any(|label| label.name == "disposition-merge")
{
Copy link
Member Author

Choose a reason for hiding this comment

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

In practice this shoudn't be prone to race conditions because disposition-* gets applied during proposed-final-comment-period already.

&& e.issue
.labels
.iter()
.any(|label| label.name == "disposition-merge")
Copy link
Member

Choose a reason for hiding this comment

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

Could you add parentheses or perhaps extract let is_fcp_merge = ...?

Copy link
Member Author

Choose a reason for hiding this comment

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

Applied.

@fmease fmease force-pushed the relnotes-tracking-must-be-disposition-merge branch from 5642640 to e72f53c Compare February 16, 2025 23:39
@Mark-Simulacrum Mark-Simulacrum merged commit 646091b into rust-lang:master Feb 18, 2025
3 checks passed
@fmease fmease deleted the relnotes-tracking-must-be-disposition-merge branch February 18, 2025 08:51
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants