TagBot setup with registry hook broken

[IanButterworth]

I had set up it such that any new registered version on HolyLabRegistry called back to TagBot on the package repo to create the new tag & release. It requires the repository_dispatch event.

@timholy it seems a bulk TagBot update you did undid that configuration.

I've updated the TagBot.yml setup here to what I think it should be, but it needs e2e testing to be sure.
https://github.com/HolyLab/RegisterDeformation.jl/blob/aa886d30c3f642f16b17a2fac85119fcddc0c8b5/.github/workflows/TagBot.yml

It'd be good to test it before rolling it out further, but I've already cut a new release on that package.

[timholy]

CC @kdw503

[timholy]

Bumping this @kdw503

[timholy]

@kdw503 is this the same as HolyLab/RegisterMismatchCommon.jl#21? Should we do a MassInstallAction to correct this?

[kdw503]

@timholy

We were previously using:
https://github.com/HolyLab/RegisterDeformation.jl/blob/aa886d30c3f642f16b17a2fac85119fcddc0c8b5/.github/workflows/TagBot.yml

However, on the HolyLabRegistry side, it was not properly triggering the signal to the target repository. That is why we had to manually run TagBot.yml in each target repository.

I fixed the HolyLabRegistry workflow so that it now correctly triggers the target repository automatically. This means we should no longer need to manually run TagBot.yml.

However, I encountered another issue on the repository TagBot.yml side:
HolyLab/RegisterMismatchCommon.jl#20

In particular, the problem is:

"The commits modify workflow files, which GITHUB_TOKEN cannot push"

Claude recommended generating a PAT with repo (read/write) and workflow permissions and using that instead.

That is the TAGBOT_TOKEN organization secret.

I'd like to test this further to confirm there are no remaining issues. If everything works correctly, then we should be able to apply it broadly using MassInstallAction.

[timholy]

Thanks! This morning I believe TileTrees 1.0 triggered automatically: https://github.com/HolyLab/TileTrees.jl/actions/workflows/TagBot.yml

No need to get to this immediately. It's just easier for me to post issues on GitHub at the time I notice them (weekday, weekend, 3am, whatever), but that doesn't mean it's urgent.