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: GeometryOpsCore v0.1.0 #116495

Merged

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Oct 3, 2024

JuliaRegistrator referenced this pull request in JuliaGeo/GeometryOps.jl Oct 3, 2024
* Factor all core stuff out into a GeometryOpsCore package

This basically guts the `types.jl` and `primitives.jl` files from GeometryOps and puts them into a new, low-dependency module that other packages can utilize for a convenient structure.

* Define `Manifold` and subtypes Linear, Spherical, Geodesic

The name `Manifold` is up for debate, I just wanted some supertype for dispatch constraints.

* Fix integration issues, get things working

* Fix import error

* Finish Project.toml and README

* Get docs to cover core + extensions also

* Fix typo

* push things properly

* amend paths too

* fix again
Copy link
Contributor

github-actions bot commented Oct 3, 2024

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.

@JuliaRegistrator JuliaRegistrator force-pushed the registrator-geometryopscore-05efe853-v0.1.0-8518a9816a branch from 0fb7ecb to 84cff09 Compare October 3, 2024 01:02
JuliaRegistrator referenced this pull request in JuliaGeo/GeometryOps.jl Oct 3, 2024
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-geometryopscore-05efe853-v0.1.0-8518a9816a branch from 84cff09 to bfb1381 Compare October 3, 2024 01:16
JuliaRegistrator referenced this pull request in JuliaGeo/GeometryOps.jl Oct 3, 2024
UUID: 05efe853-fabf-41c8-927e-7063c8b9f013
Repo: https://github.com/JuliaGeo/GeometryOps.jl.git
Tree: 8e0c68d19b0d9624d720cb2b4ab075ccf6c82650

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-geometryopscore-05efe853-v0.1.0-8518a9816a branch from bfb1381 to bf6db6f Compare October 3, 2024 15:22
@JuliaTagBot JuliaTagBot merged commit ffcb3b0 into master Oct 6, 2024
11 checks passed
@JuliaTagBot JuliaTagBot deleted the registrator-geometryopscore-05efe853-v0.1.0-8518a9816a branch October 6, 2024 00:55
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