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

Isn't is possible to unify the project/package/etc. names? #683

Closed
fuszenecker opened this issue Jan 24, 2017 · 4 comments
Closed

Isn't is possible to unify the project/package/etc. names? #683

fuszenecker opened this issue Jan 24, 2017 · 4 comments
Labels
v3.0 Changes awaiting the next breaking release
Milestone

Comments

@fuszenecker
Copy link

GitHub repo: dapper-dot-net
NuGet: dapper
NuGet title: Dapper dot net

@NickCraver
Copy link
Member

I'm all for renaming the repo and NuGet Title personally. On GitHub though, will all the /dapper-dot-net refs alias correctly, or break? That's why we've been hesitant to change these...

@NickCraver
Copy link
Member

Update: they do forward, @mgravell thoughts?

Redirect details: https://help.github.com/articles/renaming-a-repository/

@fuszenecker
Copy link
Author

fuszenecker commented Jan 25, 2017

Thanks for the info, Nick, sounds great.
Interestingly, the Title of the initial versions of Dapper was "Dapper" instead of "Dapper dot net" :-)
Something might have changed meanwhile.

@NickCraver NickCraver added the v3.0 Changes awaiting the next breaking release label Jan 28, 2017
@NickCraver NickCraver added this to the v2.0 milestone Jan 30, 2017
NickCraver added a commit that referenced this issue Feb 9, 2017
@NickCraver
Copy link
Member

This is done for the next build - the repo has been renamed as well. Thanks for the action item!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v3.0 Changes awaiting the next breaking release
Projects
None yet
Development

No branches or pull requests

2 participants