New package: ElectronWraper v1.0.0

[JuliaRegistrator]

• Registering package: ElectronWraper
• Repository: https://github.com/anke1460/ElectronWraper
• Created by: @anke1460
• Version: v1.0.0
• Commit: d25464b04b567c1a2e309b552379e163e4b9de35
• Git reference: main

[github-actions[bot]]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• Repo URL does not end with /name.jl.git, where name is the package name

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simply retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines

---

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. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[goerz]

https://github.com/JuliaRegistries/General/pull/103254#issuecomment-2008622906:

Also: how does this package relate to https://github.com/davidanthoff/Electron.jl?

yes, it fork Electron.jl, and I update to electron latest version

In most circumstances, forks of existing packages are not suitable for registration. You should try to contribute your changes to Electron.jl

[cormullion]

The spelling mistake in the name is unfortunate.

[goerz]

Yes, that would have to be fixed.

But a fork of an existing package should not be registered anyway. Although I’m not sure this really is a fork.

@davidanthoff, can you have a look at this?

[PallHaraldsson]

It seems to be a fork (and thus should be objected to), I at least see "FORK Electron.jl and update to electron V29.1.4"

@anke1460 if this is just a trivial update then please help get it into current Electron.jl with a PR there. For just you, and even others, you could use your package as unregistered, and just rename it back to Electron. I don't find it better to add Wrapper (without the type) or Fork ending. In extreme cases a package needs to be forked, and we should likely have a policy about registering such packages, and discussion about best names to use then. For open source it needs to be a "nuclear option" (seemingly no needed here, see e.g. XEmacs fork case and SXEmacs fork of fork), but not all will agree, so it NEEDS not be accented for registration.

[github-actions[bot]]

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]