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

Re: How to "pre-populate" a git message

From
DSDirk Süsserott <newsletter@dirk.my1.cc>
Date
Dec 3, 2010, 19:36 UTC
Message-ID
<4CF946C8.6050009@dirk.my1.cc>
In-Reply-To
<AANLkTim=dVxVLL31aEBrjw7OhXpdYOjAO9Sk16gGP3zJ@mail.gmail.com>
Am 03.12.2010 18:51 schrieb Patrick Doyle:
Show 11 quoted lines
> Once in a while, I would like to run some scripts that will
> automatically generate some files that I keep maintained in my
> repository.
>
> I also like to review the files before they get committed.
>
> Is there any way I can "pre-populate" the commit message so that I can
> run my "regenerate" command, review the differences, and then commit
> the changes with my prewritten message?
>
> --wpd

You can either commit the changes with the "-m <msg>" or with the "-F <file>" switch. In your case I'd suggest the latter:

1. regenerate your files and include a step that generates
    a commit message and stores that in a file, say "commit.msg".
2. review the changes
3. add all your files (except for "commit.msg", of course)
4. commit:
      $ git commit -F commit.msg

The other way would be the -m switch, but then you'd have to supply the message by yourself somehow: $ git commit -m "These files were generated at ..."

HTH,
     Dirk
Previous: Jonathan Nieder
Message 3 of 3 in “How to "pre-populate" a git message”
  1. Patrick DoyleDec 3, 2010
  2. Jonathan NiederDec 3, 2010
  3. Dirk SüsserottDec 3, 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.