git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Commiting automatically

From
MMaaartin <grajcar1@seznam.cz>
Date
Sep 24, 2010, 20:43 UTC
Message-ID
<loom.20100924T224155-693@post.gmane.org>

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

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.

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.

PS: I don't want to post separate "thank you" messages, so let me thank to 
everybody now. I've already had three questions and got three times a very 
helpful answer in a very short time, just fantastic.
Next: Ramkumar Ramachandra
Message 1 of 5 in “Commiting automatically”
  1. MaaartinSep 24, 2010
  2. Ramkumar RamachandraSep 25, 2010
  3. Alex RiesenSep 25, 2010
  4. MaaartinOct 10, 2010
  5. Matthieu MoyOct 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.