-
Notifications
You must be signed in to change notification settings - Fork 28
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
TagBot trigger issue #41
Comments
Triggering TagBot for merged registry pull request: JuliaRegistries/General#47378 |
Triggering TagBot for merged registry pull request: JuliaRegistries/General#86136 |
Triggering TagBot for merged registry pull request: JuliaRegistries/General#118877 |
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. |
16 similar comments
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
@gdalle Do you know what is going on here with TagBot? |
No, but I had the same issue with DifferentiationInterface when I added TagBot there. In both cases I copy pasted the YAML from the TagBot README a few days ago. The weirdest part is that TagBot works, it correctly detects the registration and triggers a release, so I don't know what more it needs from me |
|
Apparently it's expected behavior? |
I think manually reactivating the workflows helped. The
not sure how up to date this is though. |
Good idea, see #68 |
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.
If you'd like for me to do this for you, comment
TagBot fix
on this issue.I'll open a PR within a few hours, please be patient!
The text was updated successfully, but these errors were encountered: