Skip to content

Commit

Permalink
[AutoMerge] Do not add "blocked" label if already there (#582)
Browse files Browse the repository at this point in the history
  • Loading branch information
@giordano
giordano authored Dec 8, 2024
1 parent 8a5f46e commit 22ad11e
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "RegistryCI"
uuid = "0c95cc5f-2f7e-43fe-82dd-79dbcba86b32"
authors = ["Dilum Aluthge <dilum@aluthge.com>", "Fredrik Ekre <ekrefredrik@gmail.com>", "contributors"]
version = "10.9.0"
version = "10.9.1"

[deps]
Base64 = "2a0f44e3-6c83-55bd-87e4-b1978d98bd5f"
Expand Down
6 changes: 3 additions & 3 deletions src/AutoMerge/cron.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -313,9 +313,9 @@ function cron_or_api_build(
# of the other steps (e.g. automerge passing, waiting period, etc).
blocked = pr_has_blocking_comments(api, registry, pr; auth=auth) && !has_label(pr.labels, OVERRIDE_BLOCKS_LABEL)
if blocked
if !read_only
# add `BLOCKED_LABEL` to communicate to users
# that the PR is blocked from automerging
if !read_only && !has_label(pr.labels, BLOCKED_LABEL)
# add `BLOCKED_LABEL` to communicate to users that the PR is blocked
# from automerging, unless the label is already there.
GitHub.add_labels(api, registry.full_name, pr_number, [BLOCKED_LABEL]; auth=auth)
end
@info(
Expand Down

2 comments on commit 22ad11e

@ericphanson
Copy link
Member

Choose a reason for hiding this comment

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

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/120966

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v10.9.1 -m "<description of version>" 22ad11e9429e64d4bc096d1039330a872e1ea15f
git push origin v10.9.1

Please sign in to comment.