Migrating: weaver-test - Githubissues

typelevel / governance

Typelevel governance

Creative Commons Attribution 4.0 International

8 stars 1 forks source link

Migrating: weaver-test #114

Open rossabaker opened 12 months ago

rossabaker commented 12 months ago

Migration Checklist

Project Submission Issue: #112

For Organization Projects:

[x] Create a team for the repo with maintainer as team member
[x] After repo transfer, add repo with write permissions to the created team

For All Projects:

[ ] Add project to the site by adding an entry to the projects.yml file

Announcements

These steps are optional but encouraged.

[ ] Write a blog post announcing the change
[ ] Post to our social channels (Mastodon)

Baccata commented 12 months ago

Regarding the fact that I'm gonna have to fork instead of transferring ownership, should I create an "orphan" fork ? (Namely push the sources to the new repo without using the "fork" button)

armanbilge commented 11 months ago

What are the pros/cons?

I initially created http4s/hpack as a fork of twitter/hpack but then recently asked GitHub to decouple it. Seems to have worked fine.

https://github.com/http4s/hpack

Baccata commented 11 months ago

Oh, didn't know you could decouple after a fork. coolsies