No TagBot trigger issue opened for new package

[junyuan-chen]

Does the TagBot.yml shown on README.md give sufficient permission? I used this setting but there is no TagBot trigger issue opened when a new package is registered on General registry. Manually starting the workflow gets things work, but that issue was not created as expected.

[singularitti]

Is it possible that the bot comments @JuliaRegistrator register in a commit message? Like below:

[JuliaRegistrator]

Error while trying to register: Register Failed
@singularitti, it looks like you are not a publicly listed member/owner in the parent organization (JuliaRegistries).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[junyuan-chen]

@singularitti Thanks for replying! This is indeed how I registered the package. In case more context is needed, here is the link: junyuan-chen/ConfidenceBands.jl@24c1541

I made several packages and this was the first time I encountered such a problem. The only difference I made was that I used the updated TagBot.yml on README.md. That's why I suspected this could be the cause.

[singularitti]

I do not have this problem but the Tag Bot does seem to have other bugs recently. I hope someone could have a look at it.

[ViralBShah]

It seems to be working fine for a while now.

[anchal-physics]

I'm facing same issue on multiple repositories:

Repositories

https://github.com/ProjectTorreyPines/IMASggd.jl

https://github.com/ProjectTorreyPines/SOLPS2imas.jl

Action setup

Both repositories are using reusable workflow definition stored in https://github.com/ProjectTorreyPines/GitHubActionsWorkflows/blob/master/.github/workflows/tag_bot.yml

Note that this reusable workflow uses the same file as described on README.md but I renamed the file to tag_bot.yml to match filename case with other files.

Description of issue

First I tried this in IMASggd while registering 2.0.1 . The registration went through fine but the TagBot did not get triggered. No issue was created and thus no comment was made by JulaTagBot. I thought that maybe the issue is that JuliaTagBot is looking for a TagBot.yml file in the workflow directory and since I changed the name of the file, it could not verify if TagBot action is active or not (although it was visible as TagBot actions in list of available actions in GitHub webpage). Then, I first tried to run the workflow manually to make sure everything else is fine. And it is. The workflow ran fine and generated the new tag.

So to test the 'file name not matching' hypothesis, in another repo, SOLPS2imas, where I was also releasing a new version, I added TagBot with the filename as TagBot.yml but I face the same issue as before. No new issue was opened by JuliaTagBot and no comment was made because of which the action never triggered.

Not sure what is wrong. Should I open a new issue called "TagBot trigger issue" and close it and hope JuliaTagBot will be able to write comments on it in future?

[ViralBShah]

I suggest at least opening a new issue (since it has been working reliably and might have broken for some other reason this time).