-
Notifications
You must be signed in to change notification settings - Fork 474
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: SMILES v0.1.0 #11450
New package: SMILES v0.1.0 #11450
Conversation
JuliaRegistrator
commented
Mar 23, 2020
•
edited
Loading
edited
- Registering package: SMILES
- Repository: https://github.com/caseykneale/SMILES.jl
- Created by: @caseykneale
- Version: v0.1.0
- Commit: 72415dea47608ce36a46bd3c888fb16ca49fa9fe
- Reviewed by: @caseykneale
- Reference: v0.1.0 caseykneale/OpenSMILES.jl#1 (comment)
Your
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. Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1 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 |
Just a heads up SMILES stands for : Simplified molecular-input line-entry system Also compathelper fixed my compat issues... Do I need to do anything to fix them in here? [noblock] |
Retrigger Registrator. This will update the pull request. [noblock] |
Would it make more sense to call it [noblock] |
UUID: 29c4880b-f2d1-40f2-9463-012547100b04 Repo: https://github.com/caseykneale/SMILES.jl.git Tree: 0e71671de5d4522e57716fa48b0567fc8b710fae Registrator tree SHA: unknown
4441437
to
151ab28
Compare
It could, my concern is - my port of opensmiles might not be perfect :( [noblock] |
It's up to you. I think [noblock] |
whats the process to rename a package? Do I have to rename the repo and everything? Will anything break if I just manually change stuff? If its a big hassle I'll just stick with SMILES [noblock] |
You’d have to rename the GitHub repository, and do a find/replace inside your repo. [noblock] |
rename was successful made a new PR I guess? #11506 |