-
Notifications
You must be signed in to change notification settings - Fork 174
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
Consider moving the project to an org #243
Comments
AFAIK, you can move a repository without losing any of these. |
yeah, you can move a repo and retain commit history, issues, etc, it would be just like a rename. Also, there is automatic redirection from the old to the new repo, so even importing code via |
github.com/coredhcp/dhcp
Inspired by the |
I'm for it. |
Reviving this, would it make sense to move it to an org? |
No objections, I would use the existing coredhcp org though |
I am only opening this to discuss whether we should move the project to
github.com/coredhcp/dhcp
.The cons are that we already have the issues, stars and metrics in the current repo.
The text was updated successfully, but these errors were encountered: