Registering packages not hosted on github

Hi,
Is it possible to register a package that is hosted not on GitHub/GitLab (Codeberg in my case)?
Regards, Adam

1 Like

Yes, but you have to create the PR to the registry manually, ideally using LocalRegistry.jl.

4 Likes

Thanks! I’ve created my local registry and added my package. Could you please give me a hand and point me what exactly should I make the PR with using my local registry?

1 Like

Ah, I didn’t mean you should create your own registry, but using LocalRegistry to register your package in a local clone of the General registry. Then you just make a pull request to that repository with your change.

4 Likes

Silly me, that’s so obvious :slight_smile: Thanks!

I did so. Could you please let me know if there is anything more I should do now, or wait for merging my PR? Any idea how long it might take?
Regards, Adam

1 Like

Thanks!

Sorry for reviving this old post, but I’d like to ask how long does it take to merge the pull request made this way? All checks are passed and my package has been hanging there since yesterday waiting for merging.

If it is a newly registered package there is a 3 day wait period: GitHub - JuliaRegistries/General: The official registry of general Julia packages

4 Likes

Thanks! What if my package is submitted manually, not via Registrator.jl?

Maybe writing a message on the Julia Slack could help get the attention of someone relevant: The Julia Language Slack

All new packages have a 3 day waiting period (whether from Registrator.jl or not). If there is some special circumstance (e.g. around JuliaCon “my talk is tomorrow” is a semi-common one), then ask in #pkg-registration on Slack for an expedited merge and explain why.

The difference with Registrator vs not in terms of merging is that Registrator-powered PRs can be automerged after 3 days if all the guidelines are met: Automatic merging guidelines · RegistryCI.jl.

If the PR isn’t automerge-able (e.g. because it’s not a Registrator PR, or it is but not all the guidelines are met) one can ask on #pkg-registration on Slack for a manual merge after the 3 day waiting period.

It’s suggested in general to use Registrator and follow all the guidelines so that manual intervention is not needed, since it can take some time before someone has a chance to take a look and it isn’t scalable.

2 Likes

Personally, I would mirror it to GitHub or GitLab and register releases from there. Another option would be to add support for Codeberg to Registrator.jl (probably starting by adding support to GitHub - JuliaWeb/GitForge.jl: Unified interface for interacting with Git forges). Manually registering each release is also possible, but note every individual version will need to be manually merged, not just new package registrations.

1 Like

Thank you for clarifying.
I’m not going to put my code in GitHub or GitLab (mostly due to ideological issues).
I’ll try helping with GitForge.jl. Meanwhile, I’ll go the manual way.

what is wrong with gitlab? It is open source and you could even host your own copy (I think?). Also, I just checked JuliaHub’s “register your package” feature and they support “bare git”, so maybe that can be made to work for you:

I’ve tried JuliaHub, unfortunately I get the following error: “Cannot verify whether user is authorized to register”.

Could be worth filing an issue showing what you tried and what it showed, though maybe they just don’t support it.

1 Like

I just did so.

1 Like

That won’t work, the JuliaHub Registrator Web UI currently only works for GitHub and GitLab repos: Web UI · Registrator.jl.

Start by opening issues/PRs on the GitForge.jl and Registrator.jl repos, IMO.

Thanks, I just did so.