-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Replace the original repo in go-awesome #5
Comments
this is great. Let me update the readme. also, maybe someone can add me as a contributor? |
Sure would be nice to have more than one contributor. |
@mattes I've added you as a collaborator to both the org and the repo |
I'll update the README in migrate. Is there any way to transfer the issues as well? |
It doesn't look like there's a way to transfer issues between github repos: holman/ama#413 But there's an open source tool that uses the Github API to move issues: https://github.com/google/github-issue-mover It may be easier to give others admin access to the original repo, coveralls, and package cloud. Then we could close fork after merging/back-porting the changes. |
Looks like this was done: avelino/awesome-go#1930 |
As the original repo has been abandoned (mattes/migrate#311), this fork should replace the original repo in go-awesome.
The text was updated successfully, but these errors were encountered: