You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are no hard requirements, but it is highly recommended to follow the package naming guidelines.
But the package naming guidelines do not specify that the package name has to be `Damerau-Levenshtein distance needs to be above 2' for automerging to work. In my opinion, this restriction is too strong and should be set to 1 instead of 2. But even if it is set to 2, we have no pre-assessment tool if the julia package name we are planning for is available and allowed or not. Please provide a tool that runs your automerge requirements on package name on a webpage or somewhere so that we can validate the name.
The text was updated successfully, but these errors were encountered:
Note that "automerge fails" != "the package name is invalid". We make exceptions to the automatically checked rules. But having a way to run the automerge name checks before registration doesn't seem unreasonable to me.
I think it would be cool to have a web tool where you can enter a name and it could run and surface the checks. I don't think it would be worth the increased maintenence cost relative to just providing a function in RegistryCI like JuliaRegistries/RegistryCI.jl#453 though; it seems like something that would end up as nice for a bit until it breaks at some point and goes unmaintained.
https://github.com/JuliaRegistries/General/blob/master/README.md#are-there-any-requirements-for-package-names-in-the-general-registry says
But the package naming guidelines do not specify that the package name has to be `Damerau-Levenshtein distance needs to be above 2' for automerging to work. In my opinion, this restriction is too strong and should be set to 1 instead of 2. But even if it is set to 2, we have no pre-assessment tool if the julia package name we are planning for is available and allowed or not. Please provide a tool that runs your automerge requirements on package name on a webpage or somewhere so that we can validate the name.
The text was updated successfully, but these errors were encountered: