We have a two tier setup.
We have a primary repository (called 'primary' below).
And a secondary repository (called 'secondary' below) that was created like so:
$ git clone --bare --shared $REPO_A/primary secondary.git
People working on the secondary repository view the branches which originated from the primary repository as read only but base their own branches off these branches.
We want to sync up the secondary repository with the primary repository once a day.
I.e. we want commits and new branches that were pushed to the primary to become visible to people working off the secondary repository (next time they do a pull).
We do not want this to be symmetric, i.e. activity against the secondary repository will not become visible to those working off the primary repository.
Ideally I'd like to run a cron job that runs on the machine with the bare secondary repository that somehow fetches new data from the primary and automatically includes it into the secondary.
I was hoping there might be a simple way to do this (and I'm hoping someone here will tell me there is).
If I were to write a script to do it, it would do:
Create a fresh clone of the secondary.
$ git clone $REPO_B/secondary $ cd secondary
Get all its branches.
$ git branch -r | sed 's?.*origin/??'
Get all branches in the primary repo.
$ git ls-remote --heads $REPO_A/primary | sed 's?.*refs/heads/??'
For each primary branch for which I don't already have a corresponding secondary branch:
$ git fetch $REPO_A/primary $BRANCHNAME:$BRANCHNAME $ git push origin $BRANCHNAME:refs/heads/$BRANCHNAME
For each primary branch for which I already have a corresponding secondary branch:
$ git checkout -b $BRANCHNAME --track origin/$BRANCHNAME $ git pull $REPO_A/primary $BRANCHNAME $ git push
As I'm new to git I wouldn't be surprised if I've failed to consider certain fundamental issues?
And like I said I'm hoping there's a simpler way of doing this, i.e. someone goes "oh, don't do all that, just do...".
In their own local copies of the project, they edit files and commit changes as they would with SVN; however, these new commits are stored locally - they're completely isolated from the central repository. This lets developers defer synchronizing upstream until they're at a convenient break point.
Just for the record, you can clone a git repo within another one: Everything under your lib directory will be ignored by the enclosing Git repo, because said lib directory contains a . git . That means cloning the enclosing repo, and you will get an empty " lib/ " folder.
Oh, don't do all that, just do:
git --bare fetch
;)
(See this old thread for instance)
If you have added the relevant remote origins to your bare repo, you can fetch in turn each of those origins.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With