New package: GridMaps v0.1.0

[JuliaRegistrator]

• Registering package: GridMaps
• Repository: https://github.com/ngharrison/GridMaps.jl
• Created by: @ngharrison
• Version: v0.1.0
• Commit: 832a70ac8c8b847fcced71c78229bfeefcc7b555
• Reviewed by: @ngharrison
• Reference: ngharrison/GridMaps.jl@832a70a#commitcomment-149606490
• Description: A package for mapping quantities over rectangular grids.
• Release notes:

The first release of the GridMaps package. Provides a simple type for mapping values over rectangular grids.

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

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.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[ngharrison]

Cancel this please.

[noblock]

[goerz]

Closing in favor of #120233

For what it's worth, these "name similarity" checks are usually false positives, and can be easily overridden. GridMaps would definitely have been okay with respect to Gridap

[noblock]

[ngharrison]

@goerz Thank you. Good to know since this is the first time I've tried registering a package. How does the override work? Is that something I do or on the General registry admin side?

In the case of this package I'm trying to register, I would happily roll it back to the previous name since it aligns more with Julia package naming conventions.

[noblock]

[goerz]

Is that something I do or on the General registry admin side?

It’s on the admin side. Anyone who is at least a “triage member” (that would be me) can set it

In the case of this package I'm trying to register, I would happily roll it back to the previous name since it aligns more with Julia package naming conventions.

That would be fine. I think we actually could just reopen this PR, but then you should roll back the rename on the repo first. Or make a new registration PR, it doesn’t matter that much.

[noblock]

[ngharrison]

Ok, I've reset the name back and we can close the other pull request in favor of this one. Thanks again for your help.

[noblock]

[goerz]

[noblock] Ok, hopefully this will work, then.

We both have to edit all of our comments to contain [noblock] as well