Re: Commiting automatically

Hi Maartin,

Maaartin writes:

I'm going to run periodically a process which uses the current working tree and 
I'd like to protocol what happens. As a part of the protocol I need the exact 
state of the working tree and that's what is git good for, right? But it must 
neither disturb my normal workflow nor interfere with my ordinal commits. I 
could probably use something like

GIT_DIR=a_special_git_dir
git reset --soft a_special_branch
git add -A
git commit -m "automatic"
git push

Instead of doing it by hand, I'd recommend using something nicer like
Flashbake to do this [1].

where the push would go to my ordinary external repository (used as a backup 
here). I'm quite a beginner and unsure what problem should I expect here.

I suppose you can create another branch without common ancestry and
keep committing there. I'd suggest using contrib/git-new-workdir to
keep a working copy of that branch and using flashbake to commit to it
without interrupting your working branch.

Even if there were no problems, it's not very nice. It uses an additional 
repository which is quite strange. Moreover, there's no way to find out how the 
saved working tree snapshot is related to existing ordinal commits.

The additional repository is eliminated now. You can use the complete
Git infrastructure to play with the commits in your working branch and
your flashbake branch.

-- Ram

[1] http://bitbucketlabs.net/flashbake/