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

TagBot trigger issue #41

Closed
JuliaTagBot opened this issue Oct 23, 2021 · 27 comments
Closed

TagBot trigger issue #41

JuliaTagBot opened this issue Oct 23, 2021 · 27 comments

Comments

@JuliaTagBot
Copy link

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!

@JuliaTagBot
Copy link
Author

Triggering TagBot for merged registry pull request: JuliaRegistries/General#47378

@JuliaTagBot
Copy link
Author

Triggering TagBot for merged registry pull request: JuliaRegistries/General#86136

@JuliaTagBot
Copy link
Author

Triggering TagBot for merged registry pull request: JuliaRegistries/General#118877

@JuliaTagBot
Copy link
Author

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.

16 similar comments
@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@JuliaTagBot
Copy link
Author

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.

@simonschoelly
Copy link
Member

@gdalle Do you know what is going on here with TagBot?

@gdalle
Copy link
Member

gdalle commented Nov 10, 2024

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

@simonschoelly
Copy link
Member

Apparently the workflow was disabled because it had not run in 60 days. I enabled it now. Not sure if that helps.

tagbot

@simonschoelly
Copy link
Member

TagBot fix

@gdalle
Copy link
Member

gdalle commented Nov 10, 2024

@simonschoelly
Copy link
Member

I think manually reactivating the workflows helped. The v0.7.1 tag was only created now. Perhaps we need to do the same thing that is described in that Discourse thread in the first post here, namely add a line to the workflow

name: TagBot
on:
  issue_comment:  # THIS BIT IS NEW
    types:
      - created
  workflow_dispatch:
jobs:
  TagBot:
    # THIS 'if' LINE IS NEW
    if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
    # NOTHING BELOW HAS CHANGED
    runs-on: ubuntu-latest
    steps:
      - uses: JuliaRegistries/TagBot@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          ssh: ${{ secrets.DOCUMENTER_KEY }}

not sure how up to date this is though.

@gdalle
Copy link
Member

gdalle commented Nov 10, 2024

Good idea, see #68

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

No branches or pull requests

3 participants