Skip to content

New package: Kora v0.1.0#157005

Open
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-kora-63f594c6-v0.1.0-7367c1d0f9
Open

New package: Kora v0.1.0#157005
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-kora-63f594c6-v0.1.0-7367c1d0f9

Conversation

@JuliaRegistrator
Copy link
Copy Markdown
Contributor

UUID: 63f594c6-e77c-4cfd-819e-df68f57e9897
Repo: https://github.com/open-AIMS/Kora.jl.git
Tree: b3088f07f38348bc61fbe7d5ad2ff6a48b9f49c3

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2026

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 which are not met ❌

  • Name is not at least 5 characters long
  • I was not able to install the package (i.e. Pkg.add("Kora") failed). See the AutoMerge logs for details.
  • No licenses detected in the package's top-level folder. An OSI-approved license is required.
  • I was not able to load the package (i.e. import Kora failed). See the AutoMerge logs for details.

3. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. 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
Copy link
Copy Markdown
Member

goerz commented Jun 3, 2026

[noblock] The name should be okay, but the other issues have to be fixed before this can be merged

@ConnectedSystems
Copy link
Copy Markdown

Thank you @goerz , I'm looking into why it says the package can't be imported.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Jun 3, 2026
@goerz
Copy link
Copy Markdown
Member

goerz commented Jun 3, 2026

You should add a full test suite that runs in GitHub actions. That should reveal the issue, but it’s also a hard prerequisite for any package I would merge manually

@goerz goerz added the Override AutoMerge: ignore blocking comments Instructs automerge to ignore blocking comments label Jun 3, 2026
@JuliaTagBot JuliaTagBot removed the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Jun 3, 2026
@goerz
Copy link
Copy Markdown
Member

goerz commented Jun 3, 2026

Please make sure to follow the recommendations of https://modernjuliaworkflows.org/sharing/

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