New package: JuliaCheck v0.2.0

[JuliaRegistrator]

• Registering package: JuliaCheck
• Repository: https://github.com/tiobe/JuliaCheck
• Created by: @bellon-tiobe
• Version: v0.2.0
• Commit: 8701e3d125427f66e21ab27346f5b444e388be2b
• Reviewed by: @bellon-tiobe
• Reference: tiobe/JuliaCheck.jl@8701e3d#r161184582
• Description: Code checker for Julia language

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

• Lowercase package name juliacheck contains the string "julia".
• Repo URL does not end with /name.jl.git, where name is the package name
• There is no compat entry for julia.
• I was not able to load the package (i.e. import JuliaCheck failed). See the AutoMerge logs for details.
• Package name similar to 1 existing package.
  1. Similar to JuliaChem. 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.

[bellon-tiobe]

Stopping registration: I will rename the repository and improve the README and Project.toml files.

[GunnarFarneback]

For

I was not able to load the package (i.e. import JuliaCheck failed). See the AutoMerge logs for details.

cf. carlobaldassi/ArgParse.jl#106 (comment), or in summary, ArgParse.@project_version without argument is fundamentally broken.

[bellon-tiobe]

For

I was not able to load the package (i.e. import JuliaCheck failed). See the AutoMerge logs for details.

cf. carlobaldassi/ArgParse.jl#106 (comment), or in summary, ArgParse.@project_version without argument is fundamentally broken.

I am still trying to figure out where to see those logs, where I would see that ArgParse.@project_version is the cause of the package load failure.

Now, in addition, I wonder which argument would ArgParse.@project_version require, when it is meant to extract the project's version and pass it to ArgParseSettings (or that was my understanding, anyway).

[GunnarFarneback]

GitHub is making it more and more difficult to find the logs, but start with the "Checks" tab at the top of this page and try to find your way.

I'm not a user of ArgParse but it probably needs an argument like joinpath(@__DIR__, "..", "Project.toml").

[GunnarFarneback]

Actually I'm not sure how the macro can be used correctly at all. The function form looks more useful

ArgParse.project_version(joinpath(@__DIR__, "..", "Project.toml"))

[bellon-tiobe]

It seems to me like the macro is only useful without arguments, with the default path. Otherwise, as you said, better to use the function instead.

[GunnarFarneback]

Closed in favor of #134001.

[GunnarFarneback]

As already noted that the no-argument macro is also broken, but see carlobaldassi/ArgParse.jl#136.