Skip to content

New package: QGYBJ v0.1.0#144856

Closed
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-qgybj-961669e7-v0.1.0-28c2dab40a
Closed

New package: QGYBJ v0.1.0#144856
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-qgybj-961669e7-v0.1.0-28c2dab40a

Conversation

@JuliaRegistrator
Copy link
Contributor

UUID: 961669e7-04c5-4537-a859-b8655c92fdd1
Repo: https://github.com/subhk/QGYBJ.jl.git
Tree: 9bfe90f44c942d48b850ee2bddbc922435e89b40

Registrator tree SHA: be588f25c435fa5b456b986adf2f5c02bd3298f2
@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.

  • The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: SpecialFunctions

    Extended explanation

    Your package has a Project.toml file which might look something like the following:

    name = "YourPackage"
    uuid = "random id"
    authors = ["Author Names"]
    version = "major.minor"
    
    [deps]
    # Package dependencies
    # ...
    
    [compat]
    # ...

    Every package listed in [deps], along with julia itself, must also be listed under [compat] (if you don't have a [compat] section, make one!). See the Pkg docs for the syntax for compatibility bounds, and this documentation for more on the kinds of compat bounds required for AutoMerge.

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
Member

goerz commented Dec 23, 2025

Closing in favor of #144857

Although my recommendation would have been to choose a name that combines the acronym with prefix/suffix word that provides context. Something like WaveQGYBJ.

@goerz goerz closed this Dec 23, 2025
@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 23, 2025
@DilumAluthge DilumAluthge deleted the registrator-qgybj-961669e7-v0.1.0-28c2dab40a branch January 14, 2026 18:24
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