RegistryCI.jl icon indicating copy to clipboard operation
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

Results 64 RegistryCI.jl issues
Sort by recently updated
recently updated
newest added

Nothing good will come if the registered version number does not match the version number in `Project.toml` in the given treehash. That these are consistent should be verified and should...

Currently, if TagBotTriggers encounters an exception while processing a PR, the exception is thrown and TagBotTriggers exits immediately. For example, suppose that there are 100 PRs that need to be...

bug

So, for some reason, if the repository has a space in the name of the TagBot configuration file, it causes TagBot Triggers to fail. - Repository: https://github.com/ThummeTo/FMI.jl - TagBot configuration...

bug

At the beginning of the TagBot Triggers cron/schedule job, we get the list of all PRs on the General registry. For some reason, the GitHub API will sometimes return a...

bug
TagBot

Right now, we just error as soon as we hit a rate limit. Instead, we should probably do this 1. Ask GitHub when our rate limit will next reset. IIRC,...

Reverts JuliaRegistries/RegistryCI.jl#414 If we end up merging this PR, I will make follow-up PRs to revert the automatic PRs made by the auto-formatting bot.

> Your new package pull request met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. This isn't...

bug

I think we should add this check for new (regular) package registrations, since we use `endswith(name, "_jll")` to check if a dependency of a JLL package is a JLL package....

Currently, we merge it the correct time has passed between the time of PR open and the current time. Should we instead base the time on the time between the...

This is actually the most basic thing we should be checking: that no version hashes are changed. A second thing we might want to check is that we can clone...