RegistryCI.jl
RegistryCI.jl copied to clipboard
Continuous integration (CI) tools for Julia package registries, including registry consistency testing, automatic merging (automerge) of pull requests, and automatic TagBot triggers
See e.g. https://github.com/JuliaRegistries/RegistryCI.jl/pull/557 (e.g. [this CI log](https://github.com/JuliaRegistries/RegistryCI.jl/actions/runs/8869626132/job/24353919575)).
When doing this migration: https://github.com/JuliaRegistries/General/pull/100032 I accidentally dropped the `.git` from the package URL, and somehow the consistency CI didn't catch it. (fixed here: https://github.com/JuliaRegistries/General/pull/100034) It'd be good if we...
Idea from @GunnarFarneback on Slack: > The well-formedness of the PR tests could probably be sharpened. If there is no guarantee that the changes are created by RegistryTools, it should...
As discussed on Slack, this is a step towards running AutoMerge on non-Registrator PRs. We also need to tweak the `if` on General to run AutoMerge on forks. Note that...
Motivated by https://github.com/JuliaRegistries/General/pull/99899 Currently, `new_package_title_regex ` regex causes us to decide it's not a new package (nor a new version) and to exit. Instead, I think AutoMerge should run and...
Based on #548 which should get merged first closes https://github.com/JuliaRegistries/RegistryCI.jl/issues/413, which is a recurring source of confusion on our private registry that uses a much lower number here
Based on #547 closes #544
This is a test-only change that adds ReferenceTests as a test-dep and uses it to test the AutoMerge comment. What this allows us to do is surface changes to the...
Right now it tends to read as a bit of a wall-of-text. I think maybe we could use headings and other formatting bits to try to break it up a...
I think it should start with something like "Welcome to the General registry, and thanks for sharing your work!". That way it is less likely to be perceived as "rude"...