-
Notifications
You must be signed in to change notification settings - Fork 46
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
doc: fix confusion about the name of this package #163
doc: fix confusion about the name of this package #163
Conversation
Bug Fixes
ContributorsCommit-Lint commandsYou can trigger Commit-Lint actions by commenting on this PR:
|
When I tried to install this package, I was confused about whether it was gitlab-cli or git-lab-cli, and so I installed the package gitlab-ci and that didn't install any binaries. I have updated the README to try to reduce confusion for the next person.
26962b0
to
28ae313
Compare
I believe that I have fixed the commit comment, so I don't know why commit-lint-pr is still complaining. |
I actually wanted gitlab-cli but it was already taken in npm registry. I had created github repo long before I tried publishing on npm. I am not sure I want to take this and still keep the repo name same. That will confuse users. Also renaming repo might not be an option. Give me some time to think about this before taking call to merge or not. Please note readme does tell you how to install with correct name. |
I understand how you got there and your concern. Have you already tried contacting the author of |
I had contacted the owner of https://www.npmjs.com/package/gitlab-cli 4 years back. Didn't go well because purpose of both projects were bit different and merging those would have required a lot of work we were not ready for. |
You can almost certainly rename the repository in Github. You might need to spend a few moments to figure out all the various places where you need to change that setting, but it should work. If you'd like any help, I can try to help, although I'm a little bit of a bottleneck lately. :) I know that this isn't highly urgent, so we can take our time. |
I agree with the confusion part but none of the solutions are foolproof and bring some or the other implication or confusion. I am deciding to go against merging this. This is not solving the issue we have. We can live with what we have right now. |
When I tried to install this package, I was confused about whether it was gitlab-cli or git-lab-cli, and so I installed the package gitlab-ci and that didn't install any binaries. I have updated the README to try to reduce confusion for the next person.