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: HPCMod v0.0.1 #118396

Closed

Conversation

JuliaRegistrator
Copy link
Contributor

UUID: fd7ff580-634a-4fbd-a744-0f3e7cd44420
Repo: https://github.com/ubccr-slurm-simulator/HPCMod.jl.git
Tree: 6321f40c2d941dee136b23ff1c7652235ce13ee2

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
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 ❌

  • The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Agents, CSV, DataFrames, DataFramesMeta, DataStructures, Distributions, DocStringExtensions, Plots, Pluto, Revise, Tidier

    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.

@GunnarFarneback
Copy link
Contributor

Closed in favor of #118399.

@giordano giordano deleted the registrator-hpcmod-fd7ff580-v0.0.1-62d67f602b branch November 9, 2024 16:34
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