HolyLab / HolyLab/HolyLabRegistry
TagBot setup with registry hook broken
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/TagBot.yml in RegisterDeformation.jl at the linked revision and review how the repository_dispatch event is configured. Run an end-to-end test using a newly registered version on HolyLabRegistry; done means TagBot receives the callback and creates the expected tag and release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, julia
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100