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

Repo name does not match gem name #2

Open
majormoses opened this issue Jul 15, 2017 · 2 comments
Open

Repo name does not match gem name #2

majormoses opened this issue Jul 15, 2017 · 2 comments
Assignees

Comments

@majormoses
Copy link
Member

discovered in #1 I think this can be confusing at best and at worst maddening when troubleshooting something small like this is.

I am not sure if we should change the repo name to match the gem name or vice versa. We might also might just opt for just putting something in the readme to make it more obvious.

@majormoses
Copy link
Member Author

@majormoses
Copy link
Member Author

travis-ci/dpl#574 I have seen this when the gem was not registered, pretty sure we need to do some extra travis changes as per travis-ci/dpl#574 (comment) but my question is should we prefer to make this less one off (could make scripting stuff harder as well)

@majormoses majormoses added the Bug label Jul 15, 2017
@majormoses majormoses changed the title Gem name does not match gem name Repo name does not match gem name Sep 9, 2017
@majormoses majormoses added Type: Bug and removed Bug labels Oct 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants