Thread (9 messages) 9 messages, 7 authors, 2022-07-01

Re: Non-interactively rewording commit messages

From: Ævar Arnfjörð Bjarmason <hidden>
Date: 2022-06-30 18:11:40

On Thu, Jun 30 2022, Konstantin Ryabitsev wrote:
On Thu, Jun 30, 2022 at 07:34:54PM +0200, Christian Couder wrote:
quoted
quoted
Hello, all:

What's the best approach to non-interactively rewrite specific commit
messages? In this particular case, I am trying to automatically retrieve code
review trailers sent to the mailing list and put them into corresponding
commits.

For example, I have a set of commits:

abcabc: This commit does foo
bcdbcd: This commit does bar
cdecde: This commit does baz

They were all sent to the mailing list and a maintainer sent a "Reviewed-by"
to the second commit. In a usual interactive rebase session this would be:

pick abcabc
reword bcdbcd
pick cdecde

When the edit screen comes up for the bcdbcd commit, the author would manually
stick the new trailer into the commit message. However, I can automate all
that away with b4 -- just need a sane strategy for non-interactively rewriting
entire commit messages at arbitrary points in the recent history.

Any pointers?
Have you tried `git interpret-trailers`?
I'm aware of interpret-trailers, but unless I'm missing something large, it's
just a way of analyzing standalone text files to retrieve or insert trailers.
What I'm looking for is a way to amend arbitrary commit messages within recent
git history.
I think what's being suggested is that once you have a program that can
munge a commit message on stdin, you can combine it with rebase, git
commit --amend etc. to change existing commits.q

The t/t7513-interpret-trailers.sh test has some examples of munging
existing content.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help