Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New package: JLCL v1.0.1 #105295

Closed

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Apr 20, 2024

## Initial Release of JLCL package.

Unorthodox version number, but bear with me.

Copy link
Contributor

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

  • Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  • Name is not at least 5 characters long
  • Repo URL does not end with /name.jl.git, where name is the package name
  • No licenses detected in the package's top-level folder. An OSI-approved license is required.
  • Package name similar to 6 existing packages.
    1. Similar to JLSO. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Normalized visual distance 2.44 is at or below cutoff of 2.50.
    2. Similar to JLD2. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
    3. Similar to JLD. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
    4. Similar to JACC. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
    5. Similar to NCCL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
    6. Similar to LSL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simply retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines


If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

UUID: cc15090e-1e6b-4c7b-9eb6-d2b5646cebf8
Repo: https://github.com/marcoxa/JLCL.git
Tree: 6ea9308df7b2c7fb80ba7ce4c2520dd88094242c

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-jlcl-cc15090e-v1.0.1-d6eeb4b655 branch from ede6b97 to 0e313f4 Compare April 20, 2024 17:33
@goerz
Copy link
Member

goerz commented Apr 20, 2024

Closing in favor of #105297

@goerz goerz closed this Apr 20, 2024
@DilumAluthge DilumAluthge deleted the registrator-jlcl-cc15090e-v1.0.1-d6eeb4b655 branch May 5, 2024 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants