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

Re: Non-interactively rewording commit messages

From
Carlo Marcelo Arenas Belón <carenas@gmail.com>
Date
Jun 30, 2022, 17:32 UTC
Message-ID
<20220630173211.pnliwplmimcaygny@carlos-mbp-2.lan>
In-Reply-To
<20220630152757.yxwhijvj5xoosrws@meerkat.local>
On Thu, Jun 30, 2022 at 11:27:57AM -0400, Konstantin Ryabitsev wrote:
> just need a sane strategy for non-interactively rewriting
> entire commit messages at arbitrary points in the recent history.
assuming you are still doing it by calling (albeit programmatically):
  rebase --autosquash -i

then you could prepare the new message by also programmatically doing a `git commit --fixup reword:<commit>` IMHO

Carlo
Previous: Konstantin RyabitsevNext: Christian Couder
Message 2 of 11 in “Non-interactively rewording commit messages”
  1. Konstantin RyabitsevJun 30, 2022
  2. Carlo Marcelo Arenas BelónJun 30, 2022
  3. Christian CouderJun 30, 2022
  4. Konstantin RyabitsevJun 30, 2022
  5. Ævar Arnfjörð BjarmasonJun 30, 2022
  6. Junio C HamanoJun 30, 2022
  7. Christian CouderJul 1, 2022
  8. brian m. carlsonJun 30, 2022
  9. Elijah NewrenJul 1, 2022
  10. Konstantin RyabitsevJul 1, 2022
  11. Johannes SchindelinJul 1, 2022

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.