Skip to content

New package: PURL v0.1.0#147171

Closed
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-purl-c2271b70-v0.1.0-c77fee563c
Closed

New package: PURL v0.1.0#147171
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-purl-c2271b70-v0.1.0-c77fee563c

Conversation

@JuliaRegistrator
Copy link
Contributor

Initial registration

UUID: c2271b70-7219-4bda-bcc3-62ec08ead5b7
Repo: https://github.com/s-celles/PURL.jl.git
Tree: af91f1c35aedc073d9c868accdfc6103f0a2da9f

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@s-celles
Copy link

Superseded by #147172

@github-actions
Copy link
Contributor

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 does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.
  • Name is not at least 5 characters long
  • No licenses detected in the package's top-level folder. An OSI-approved license is required.
  • Package name similar to 2 existing packages.
    1. Similar to PDDL. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Normalized visual distance 2.30 is at or below cutoff of 2.50.
    2. Similar to IsURL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

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.

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

goerz commented Feb 4, 2026

Closing in favor of #147604

@goerz goerz closed this Feb 4, 2026
@DilumAluthge DilumAluthge deleted the registrator-purl-c2271b70-v0.1.0-c77fee563c branch February 8, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants