Update all git repositories under a base directory

update_git_repos.sh

#!/bin/bash

# store the current dir
CUR_DIR=$(pwd)

# Let the person running the script know what's going on.
echo "\n\033[1mPulling in latest changes for all repositories...\033[0m\n"

# Find all git repositories and update it to the master latest revision
for i in $(find . -name ".git" | cut -c 3-); do
    echo "";
    echo "\033[33m"+$i+"\033[0m";

    # We have to go to the .git parent directory to call the pull command
    cd "$i";
    cd ..;

    # finally pull
    git pull origin master;

    # lets get back to the CUR_DIR
    cd $CUR_DIR
done

echo "\n\033[32mComplete!\033[0m\n"

Thanks just what I needed ;)

Thanks just what I needed ;)

Depending on your echo, you might need to use echo -e for the escape color code to work.

Depending on your echo, you might need to use echo -e for the escape color code to work.

Cool. // True about "echo -e" !

Cool. // True about "echo -e" !

Thank you. I use a slight variation:

find . -name .git -type d \
| xargs -n1 -P4 -I% git --git-dir=% --work-tree=%/.. remote update -p

Using -type d prevents execution for ".git" files inside submodules. Using -P4 runs four fetches in parallel to speed things up a bit (and continues to make progress elsewhere if a single repository hangs). I prefer git remote update -p instead of git pull so that I can deal with merge conflicts later or rebase after I'm offline.

Thank you. I use a slight variation:

find . -name .git -type d \
| xargs -n1 -P4 -I% git --git-dir=% --work-tree=%/.. remote update -p

Using -type d prevents execution for ".git" files inside submodules. Using -P4 runs four fetches in parallel to speed things up a bit (and continues to make progress elsewhere if a single repository hangs). I prefer git remote update -p instead of git pull so that I can deal with merge conflicts later or rebase after I'm offline.

You need to enclose $CUR_DIR in quotes, like cd "$CUR_DIR" if $CUR_DIR happens to contain special characters. Alternatively, you could also run the loop body in a subshell (using (...)).

You need to enclose $CUR_DIR in quotes, like cd "$CUR_DIR" if $CUR_DIR happens to contain special characters. Alternatively, you could also run the loop body in a subshell (using (...)).

Thanks - h5!

Thanks - h5!

Awesome. This works just as intended ^^

Awesome. This works just as intended ^^

Thanks this is what I was looking for!

Thanks this is what I was looking for!

Call stuff! Even runs on Windows 10. 😎

Call stuff! Even runs on Windows 10. 😎

What license is associated with this Gist? MIT? Apache? DWTFYW? :)

What license is associated with this Gist? MIT? Apache? DWTFYW? :)

dmhowcroft,

Legally anything released without a copyright notice is public domain, the notice contains a year range. If you release something with a year range then a few years later you make changes without updating the copyright notice, then those changes are public domain.

It was nice of you to ask the author :)

dmhowcroft,

Legally anything released without a copyright notice is public domain, the notice contains a year range. If you release something with a year range then a few years later you make changes without updating the copyright notice, then those changes are public domain.

It was nice of you to ask the author :)

I have some gits organized with my other gits that no longer have working github pages and so when the script gets to them it asks for a username and password. Is there any way to add to the script to make it so it just enters nothing for both the username and password? (or any other way to make it skip that hangup). I'd like to keep the related gits together for organizational purposes if possible. Thank you so much for your time and this awesome and SUPER USEFUL script :)

EDIT - Also I forgot to add that I put "read" (without the quotes) at the end so I can read the text log before it closes :)

I have some gits organized with my other gits that no longer have working github pages and so when the script gets to them it asks for a username and password. Is there any way to add to the script to make it so it just enters nothing for both the username and password? (or any other way to make it skip that hangup). I'd like to keep the related gits together for organizational purposes if possible. Thank you so much for your time and this awesome and SUPER USEFUL script :)

EDIT - Also I forgot to add that I put "read" (without the quotes) at the end so I can read the text log before it closes :)

hey guys if you want i have another script here, it follows the same idea here but with many other options, i am a noob so if you have some feedback or want to contribute please let me know :D
https://github.com/devCharles/gitRepoUpdater

hey guys if you want i have another script here, it follows the same idea here but with many other options, i am a noob so if you have some feedback or want to contribute please let me know :D
https://github.com/devCharles/gitRepoUpdater

If you want this to work with submodules too, I'd suggest using a slightly altered version of @mndrix's solution:

find . -name .git -type d | xargs -n1 -P4 -I% git --git-dir=% --work-tree=%/.. fetch --all --recurse-submodules

If you need to manually enter passwords for some repos, use this instead:

find . -name .git -type d | xargs -n1 -I% git --git-dir=% --work-tree=%/.. fetch --all --recurse-submodules

The --recurse-submodules options tells git to also fetch commits from any submodules' upstream. It means that if you run this script then go offline and checkout a new version of one of your projects which references a new submodule commit, when you run git submodule update it will be still able to find the new commit.

If you want this to work with submodules too, I'd suggest using a slightly altered version of @mndrix's solution:

find . -name .git -type d | xargs -n1 -P4 -I% git --git-dir=% --work-tree=%/.. fetch --all --recurse-submodules

If you need to manually enter passwords for some repos, use this instead:

find . -name .git -type d | xargs -n1 -I% git --git-dir=% --work-tree=%/.. fetch --all --recurse-submodules

The --recurse-submodules options tells git to also fetch commits from any submodules' upstream. It means that if you run this script then go offline and checkout a new version of one of your projects which references a new submodule commit, when you run git submodule update it will be still able to find the new commit.

Perfect, thanks!

Perfect, thanks!

simple and does what is needed, thank you!

simple and does what is needed, thank you!

#!/bin/bash
# run this from your workspace, which contains all your Git repos
CUR_DIR=$(pwd)
echo "\nUpdating remotes for all repositories...\n"
for i in $(find . -mindepth 1 -maxdepth 1 -type d); do
    printf "\nIn Folder: $i";
    cd "$i";
    printf "\n"
    THIS_REMOTES="$(git remote -v)"
    arr=($THIS_REMOTES)
    OLD_REMOTE="${arr[1]}";
    NEW_REMOTE="${OLD_REMOTE/git.old.net/git.new.org}"
    printf "New remote: $NEW_REMOTE"
    printf "\n"
    git remote set-url origin "$NEW_REMOTE"
    cd $CUR_DIR
done
printf "\nComplete!\n"

#!/bin/bash
# run this from your workspace, which contains all your Git repos
CUR_DIR=$(pwd)
echo "\nUpdating remotes for all repositories...\n"
for i in $(find . -mindepth 1 -maxdepth 1 -type d); do
    printf "\nIn Folder: $i";
    cd "$i";
    printf "\n"
    THIS_REMOTES="$(git remote -v)"
    arr=($THIS_REMOTES)
    OLD_REMOTE="${arr[1]}";
    NEW_REMOTE="${OLD_REMOTE/git.old.net/git.new.org}"
    printf "New remote: $NEW_REMOTE"
    printf "\n"
    git remote set-url origin "$NEW_REMOTE"
    cd $CUR_DIR
done
printf "\nComplete!\n"

Hey guys,

thought about handling cases when there are some changes made in files or any other situation where just git pull won't succeed?

Hey guys,

thought about handling cases when there are some changes made in files or any other situation where just git pull won't succeed?

Very helpful! Thank you

Very helpful! Thank you

thanks

thanks

Thank you, very helpful. 👍

Thank you, very helpful. 👍

Simplest solution to fetch all remotes:

$ find . -name .git -type d -exec git --git-dir '{}' fetch --all ';'

Simplest solution to fetch all remotes:

$ find . -name .git -type d -exec git --git-dir '{}' fetch --all ';'