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: OneRule v0.1.0 #55912

Merged
merged 1 commit into from
Mar 6, 2022
Merged

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Mar 3, 2022

JuliaRegistrator referenced this pull request in roland-KA/OneRule.jl Mar 3, 2022
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch March 3, 2022 20:12 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2022

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.

Since you are registering a new package, please make sure that you have 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.

@JuliaRegistrator JuliaRegistrator force-pushed the registrator/onerule/90484964/v0.1.0 branch from 6db9d51 to 3141949 Compare March 3, 2022 20:39
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch March 3, 2022 20:39 Inactive
@roland-KA
Copy link

roland-KA commented Mar 3, 2022

I've changed the [compat] entry for StatsBase mentioned above. But registration seems to fail nevertheless. What can I do now? [noblock]

@giordano
Copy link
Member

giordano commented Mar 3, 2022

You have to trigger registration again as you did before, that is not here but in roland-KA/OneRule.jl@482c7b1.

Also, note that you should not create git tags manually but use instead TagBot, which will automatically create the tags after successful registration, to ensure consistency between git tags and what it's actually registered. You can delete the existing git tag and try again.

Finally, as written in the message above, if you don't want to block your own registration you should have [noblock] in all of your messages, otherwise this PR will never be merged automatically. You can edit your message above.

UUID: 90484964-6d6a-4979-af09-8657dbed84ff
Repo: https://github.com/roland-KA/OneRule.jl.git
Tree: 46d3c31db356a9f18679a046217500c1c8fb3fe1

Registrator tree SHA: 8e1a5ac2695627143951512d700c7e3c445102ec
@JuliaRegistrator JuliaRegistrator force-pushed the registrator/onerule/90484964/v0.1.0 branch from 3141949 to 8e368fd Compare March 4, 2022 00:01
JuliaRegistrator referenced this pull request in roland-KA/OneRule.jl Mar 4, 2022
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch March 4, 2022 00:01 Inactive
@roland-KA
Copy link

Hi @giordano, I've followed all of your recommendations. Will the package now automatically be registered or is there more action required from my side? [noblock]

@giordano
Copy link
Member

giordano commented Mar 6, 2022

Yes, it should be merged automatically in a couple of hours

[noblock]

@JuliaTagBot JuliaTagBot merged commit e1632a1 into master Mar 6, 2022
@JuliaTagBot JuliaTagBot deleted the registrator/onerule/90484964/v0.1.0 branch March 6, 2022 20:15
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.

4 participants