New package: MatricesForHomalg v0.1.0

[JuliaRegistrator]

• Registering package: MatricesForHomalg
• Repository: https://github.com/homalg-project/MatricesForHomalg.jl
• Created by: @mohamed-barakat
• Version: v0.1.0
• Commit: 8dff4d226dc3d6c535cd2cbeba65b4a438ae9cf3
• Reviewed by: @mohamed-barakat
• Reference: homalg-project/MatricesForHomalg.jl@8dff4d2#commitcomment-150965149
• Description: Matrices for the homalg project

[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.

[goerz]

[noblock] I would recommend adding a paragraph to the README to give some context for this package, including a link to the homalg project. Ideally, someone randomly coming across the repo should have a rough idea of what the purpose of the package is, just based on the information in the README

[mohamed-barakat]

[noblock] Yes, good idea, thank you very much.

How can I update this PR?

[goerz]

[noblock] You can just comment @JuliaRegistrator register on the new commit, and it will update this PR. It's optional, though: an update to the README doesn't really affect the release, and anyone looking at the repo will see the latest version anyway. So you don't really have to do anything