Say you are using FortRabbit, which runs its own Git repository just for deployment purposes. You want commit history and user control, so you want something else like BitBucket as your primary repository.
You can have both (wow).
Step 1: Create a new repository in BitBucket. Do NOT create a readme file. There has to be no commit history or you will receive errors from FortRabbit.
Step 2: Clone your FortRabbit repository into a new folder on your computer. Let’s use double-repo for this example.
Step 3: Follow the steps below to remove FortRabbit as double-repo‘s remote and add BitBucket. Then push all the files to BitBucket.
https://www.atlassian.com/git/tutorials/git-move-repository
Step 4: Add FortRabbit as a remote using the syntax below. This will provide a unique name for the remote (fortrabbit) rather than the default, origin:
https://help.fortrabbit.com/github
Now the repositories have shared histories. It’s important that both repositories were synched when they were new to avoid history conflicts (which are more difficult when the repositories are managed without controls, by FortRabbit for example).
Now you can:
- Push to BitBucket with
git push origin master. - Push to FortRabbit with
git push fortrabbit master. - Add new contributers to BitBucket without allowing them deployment privileges.
💩