threads / discuss / 18501

Adding a new file to all git branches

Subject: Adding a new file to all git branches

## tl;dr

2 messages between Mar 24, 2009 and Mar 24, 2009.

replies: 1people: 2as markdown or json

Aneesh Bhasin· Mar 24, 2009, 03:41 UTC · lore
Hi,

I was wondering if it is possible to add a file to all the branches in a repository without individually checking out each branch ?

A possible use-case for such a scenario is say I have a git repository with various branches related to different features, versions or bug-fixes and I want to be able to add a README file which contains instructions/information common to all of those branches as of now (but may diverge in future). So, do I have to checkout each branch individually to add the same README file to all of them or is there a direct/indirect workaround ?

Thanks for your help..

Regards, Aneesh

Jeff King· Mar 24, 2009, 06:31 UTC · re: Aneesh Bhasin · lore

Re: Adding a new file to all git branches

On Tue, Mar 24, 2009 at 09:11:15AM +0530, Aneesh Bhasin wrote:
Show 10 quoted lines
> I was wondering if it is possible to add a file to all the branches in
> a repository without individually checking out each branch ?
> 
> A possible use-case for such a scenario is say I have a git repository
> with various branches related to different features, versions or
> bug-fixes and I want to be able to add a README file which contains
> instructions/information common to all of those branches as of now
> (but may diverge in future). So, do I have to checkout each branch
> individually to add the same README file to all of them or is there a
> direct/indirect workaround ?
Not really.
You basically have three options:
 1. branch a new "README" line of development from some common ancestor
    of all branches, add the README, and then merge this new branch into
    your other branches
    The advantage of this approach is that you could actually keep the
    README branch around, making changes to it and merging it back into
    your other branches as appropriate.
    Of course, you asked about avoiding "checkout", and you will still
    have to checkout each branch to do the merge.
 2. For a one-off addition of such a README, it is probably simpler to
    just use a for loop with checkout:
      for i in branch1 branch2 branch3; do
        git checkout $i &&
        cp /path/to/README . &&
        git add README &&
        git commit -m 'add README'
      done
     Which again, obviously does checkout, but at least it's
     non-interactive. The biggest downside is that doing a full checkout
     between branches might be slow.
 3. You could also just iterate over the branches with plumbing, adding
    the README to each tree. Something like:
      hash=`git hash-object -w /path/to/README`
      for i in b1 b2 b3; do
        GIT_INDEX_FILE=index.$i; export GIT_INDEX_FILE
        git read-tree $i &&
        git update-index --add --cacheinfo 100644 $hash README &&
        tree=$(git write-tree) &&
        parent=$(git rev-parse $i) &&
        commit=$(echo added README | git commit-tree $tree -p $parent) &&
        git update-ref -m "commit: added README" refs/heads/$i $commit $parent
        rm $GIT_INDEX_FILE
        sleep 1
      done
    This is going to be faster, but obviously is much more complicated.
For a one-off addition, I would probably just do (2).
-Peff

← back to recent threads