In your usecase you can’t fork the repo, as that w...
# how-do-it
Tonko Mulder
01/04/2024, 9:11 PMIn your usecase you can’t fork the repo, as that would also be public. Probably best to create a separate private repository with the open-source repo as upstream remote.
So you’d have two remotes: origin & upstream (for example) when the work is done. You can push changes upstream
Tonko Mulder
01/04/2024, 9:14 PM Copy code
~/P/laravel-mongodb ❯❯❯ git remote -vv 4.1 ✭
origin git@github.com:/Treggats/laravel-mongodb.git (fetch)
origin git@github.com:/Treggats/laravel-mongodb.git (push)
upstream git@github.com:mongodb/laravel-mongodb (fetch)
upstream git@github.com:mongodb/laravel-mongodb (push)d
Dan Oved
01/04/2024, 9:19 PMyeah we were generally following this pattern currently...question is, lets say we have a bug fix we want to go in the public (upstream remote) repo, what would you suggest doing here? we were thinking of doing the patch in the upstream repo, then rebasing the private one from that, but that seems a bit precarious
t
Tonko Mulder
01/04/2024, 9:23 PMBecause of this approach you always need to manually keep your private (fork) repo up to date.
But yes that sounds like a reasonable approach