|
|
|
|
|
|
by w0rd-driven
3025 days ago
|
|
|
To reiterate what you're saying, a fork in this instance could be nothing more than setting up a new remote on another provider and pushing to that. Most providers have a concept of imports that work much like a fork would. Gitlab specifically will import the repo, wiki, issues, and likely other bits. Everything is treated as a snapshot in time but since the repository and wiki are both git, you can merge upstream changes later. There's also the concept of mirroring that'll automatically push or pull changes from other providers. I haven't done an import/fork to Github to know how that experience is but I've done a good few with Gitlab to know that it works rather well. |
|
|