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

Replace the original repo in go-awesome #5

Closed
dcormier opened this issue Jan 26, 2018 · 6 comments
Closed

Replace the original repo in go-awesome #5

dcormier opened this issue Jan 26, 2018 · 6 comments

Comments

@dcormier
Copy link
Contributor

dcormier commented Jan 26, 2018

As the original repo has been abandoned (mattes/migrate#311), this fork should replace the original repo in go-awesome.

@dcormier dcormier changed the title Replace the original fork in go-awesome Replace the original repo in go-awesome Jan 26, 2018
dhui pushed a commit to dhui/awesome-go that referenced this issue Jan 26, 2018
@mattes
Copy link
Collaborator

mattes commented Jan 26, 2018

this is great. Let me update the readme. also, maybe someone can add me as a contributor?

@dcormier
Copy link
Contributor Author

Sure would be nice to have more than one contributor.

@dhui
Copy link
Member

dhui commented Jan 30, 2018

@mattes I've added you as a collaborator to both the org and the repo

@mattes
Copy link
Collaborator

mattes commented Jan 31, 2018

I'll update the README in migrate. Is there any way to transfer the issues as well?

@dhui
Copy link
Member

dhui commented Jan 31, 2018

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.

@dhui
Copy link
Member

dhui commented Jun 16, 2018

Looks like this was done: avelino/awesome-go#1930

@dhui dhui closed this as completed Jun 16, 2018
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