Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[AutoMerge] Do not add "blocked" label if already there #582

Merged
merged 1 commit into from
Dec 8, 2024

Conversation

giordano
Copy link
Member

@giordano giordano commented Dec 8, 2024

Untested, but I presume this should fix #573 (comment).

Copy link
Member

@ericphanson ericphanson left a comment

Choose a reason for hiding this comment

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

good catch! I had assumed adding the label was idempotent and it was slightly better to unconditionally add it to avoid (somewhat unlikely) race conditions, such as due to pr.labels being stale. Did not realize it would bump the PR. Looks like a good fix to me.

I wonder if there's anywhere else I'm not checking due to the same kind of assumptions?

@ericphanson ericphanson added this pull request to the merge queue Dec 8, 2024
@giordano
Copy link
Member Author

giordano commented Dec 8, 2024

This seems to be the only use of add_labels

Merged via the queue into master with commit 22ad11e Dec 8, 2024
11 checks passed
@ericphanson ericphanson deleted the mg/blocked-label branch December 8, 2024 21:34
@DilumAluthge
Copy link
Member

Thank you both!

@giordano
Copy link
Member Author

giordano commented Dec 8, 2024

For the record, PRs with the "blocked" label haven't been updated en masse for over an hour, more specifically since JuliaRegistries/General#120968 was merged, so it'd appear this PR did its job.

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

Successfully merging this pull request may close these issues.

3 participants