Closed JuliaTagBot closed 4 years ago
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24366
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24535
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/37374
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42614
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50735
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/52381
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
@visr is JuliaGeo configured properly for TagBot? All repos keep sending these repeated notifications GADM.jl, GDAL.jl, ... and I wonder if this is something on our side. All other repos I maintain in other orgs don't have these notifications after a new tag is released.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61575
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62052
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62285
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63093
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75428
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/83708
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105080
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106810
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111989
This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your
TagBot.yml
to include issue comment triggers. Please see this post on Discourse for instructions and more details.