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.

Sign up for GitHub

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

Jump to bottom

New package: SpiDy v0.1.0 #87171

Merged
merged 1 commit into from
Jul 15, 2023
Merged

New package: SpiDy v0.1.0 #87171

merged 1 commit into from
Jul 15, 2023

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator
New package: SpiDy v0.1.0
31d52a7 
UUID: a4849050-cccd-45e7-a409-2b114d5ccb2f
Repo: https://github.com/quantum-exeter/SpiDy.jl.git
Tree: 2d0932760f999ffa23381ce22875cf6afac95b2a

Registrator tree SHA: f73a20c99934db92a256057d0d83ba394036a701
JuliaRegistrator referenced this pull request in quantum-exeter/SpiDy.jl Jul 10, 2023
@cerisola
Added minimum required Julia version
1cfc305
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch July 10, 2023 12:51 — with GitHub Actions Inactive
@github-actions
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:

  • Package name similar to 1 existing package.
    1. Similar to SciPy. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Normalized visual distance 2.40 is at or below cutoff of 2.50.

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, simple 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://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

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.

@mekise
Copy link

mekise commented Jul 10, 2023

I have noticed our package name does not pass the name similarity test being at the very edge of the threshold. Given the short name, therefore the high probability of similar letters in the reshuffling, is there any way to "appeal"? I believe that, even though the 2 names fall on the edge of the threshold, they look, mean and sound very different. Thanks!

@giordano giordano merged commit 40e191e into master Jul 15, 2023
@giordano giordano deleted the registrator-spidy-a4849050-v0.1.0-cab651bb71 branch July 15, 2023 17:17
@JuliaTagBot JuliaTagBot mentioned this pull request Jul 15, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
needs to be manually merged in 3 days new package Override AutoMerge: name similarity is okay
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@JuliaRegistrator @mekise @ViralBShah @giordano