Recently, I’ve been working with a lot of git repos at a time. I mean a lot. Like more than twenty. . . That’s the bad news.
The code news is the code is all passionately crafted and a joy to work with. Which is one of the reasons I try to make sure I’m always working with the latest-and-greatest before diving in.
But, I couldn’t see myself running git pull for every single respository. Believe me, I tried. . .
Git pull itself has it’s issues, so I wanted to be mindful of commit merges. In addition, I’m often helping teammates validate new features or bugfixes in bleeding edge branches, so I wanted to make sure I’m always getting the latest-and-greatest remote branches as well.
By default, git pull helps you do neither particualary well. That’s when I ran into the concept of git up.
With all versions of Git, you can configure a git alias. So I configured an alias called git up:
This alias downloads all of the latest commits from all upstream branches and tries to fast-forward the local branch to the latest commit on the upstream branch.
Using this technique, I’m able to get all remote branches while keeping the repository’s commit history clean.
But the challenge still remained of how to deal with running git up for multiple git repos.
Going Full Shell
I use a shell script to get the job done of updating multiple git repos:
It’s not perfect by any means, but it gets the job done. Some things to look out for. . .
First, you have to add a new repo to your for loop for each new repo you work with. In addition, you need to have previously git cloned the listed repo. Which makes sense because you can’t checkout a branch for a nonexistent repo.
Finally, notice the use of the git up alias we created earlier. Combining both technqiues, you’re able to reliably update multiple git repos at a time.
If you find yourself needing to update multiple git repos at a time, give this technique a try.