Timeline for Forking Git repository from GitHub to GitLab
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2023 at 22:21 | comment | added | m3lixir | The page @bellackn mentioned no longer exists, I believe it lives here now. | |
| Sep 19, 2022 at 21:48 | comment | added | Nike | @bellackn Do you know how to do it the other way around? If there's a repository on GitLab, can I fork it into a GitHub organization? | |
| Jul 14, 2022 at 4:45 | comment | added | zheyuanWang |
I recommand to add --depth=1 when pulling from a big project and you don't care about its history commits
|
|
| May 10, 2022 at 8:21 | comment | added | Zhang Fan | please note "master" is changed to "main" on Github. | |
| May 14, 2021 at 12:45 | comment | added | Paloha | @ChrisWatts thanks for the info about Mirroring in GitLab. I was not at all aware of it. | |
| Sep 3, 2020 at 10:35 | comment | added | Chris Watts |
@ErikAronesty That's trickier as "Pull Requests" aren't a git thing, rather a GitHub thing. One way to do this though is to fork a copy on GitHub and add your forked repo as another remote, say git remote add upstream-fork [email protected]:myuser/repo. Then it's just a matter of git push upstream-fork master and submit your pull request via the GitHub site.
|
|
| Aug 20, 2020 at 18:08 | comment | added | Erik Aronesty | How do you submit a pull request later? | |
| Oct 15, 2019 at 11:31 | comment | added | hmojtaba | I had to use: pull upstream master --allow-unrelated-histories | |
| Jul 10, 2019 at 8:18 | comment | added | bellackn | Just want to add that forking does exist on GitLab, see here for example. | |
| Mar 19, 2019 at 10:33 | comment | added | Bruno Finger | I would just like to complement this answer to why this is the correct approach. "Forking" is a concept created by GitHub thus only exists on GitHub, useful nonetheless. If you consider pure git itself (like a pure git server running somewhere in your network), that would be like cloning the repo to your own server and then cloning that to your local computer. You'd add the original repo as the upstream locally then. I believe that's what GitHub does behind the scenes. | |
| Oct 24, 2018 at 16:24 | history | edited | Chris Watts | CC BY-SA 4.0 |
remove typo
|
| Oct 24, 2018 at 11:10 | vote | accept | Cimlman | ||
| Oct 23, 2018 at 16:53 | history | answered | Chris Watts | CC BY-SA 4.0 |