-
Notifications
You must be signed in to change notification settings - Fork 444
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 version: GrowthMaps v0.2.2 #26452
Conversation
JuliaRegistrator
commented
Dec 16, 2020
- Registering package: GrowthMaps
- Repository: https://github.com/cesaraustralia/GrowthMaps.jl
- Created by: @rafaqz
- Version: v0.2.2
- Commit: 1c314df90f8b7e9c4d2b5f6f2bd533ae79d09ba7
- Reviewed by: @rafaqz
- Reference: cesaraustralia/GrowthMaps.jl@1c314df#commitcomment-45160730
UUID: a252ced4-3752-11e9-0615-256422162c4d Repo: https://github.com/cesaraustralia/GrowthMaps.jl.git Tree: ff6ecffcaceeaa2af611dcd55da431bc3412d28b Registrator tree SHA: e934b8c55381f28735124f23e8f7e96d09b20416
Your
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. 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 |
@rafaqz did you skip the version on purpose? |
No... just have too many packages to register and forget what I have bumped already |
What do you plan to do? Register the missing version or go on with this one? I ain't going to do anything without your input 🙂 Side note, I also maintain a fair number of packages, but helping automerge doing its work reduces the work on the (very) few people that patrol the registry, in addition to reducing the waiting time for you developers |
I registered the skipped version 1 minute after that comment ;) And apologies I entirely did not intend to cause you more work, I'll check versions more carefully in future. Maybe we should make it so this kind of basic error doesn't ask for any input. (Also I was under the misinformed impression that my second |
Not sure what you're proposing |
It doesnt make sense for your attention to be required for this
I mean of course not, right? But my other registrator push did not remove this PR, and there is no way of me manually closing it. Probably a Registrator command could help, but I dont know much about registrator to suggest anything. |