Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Paul Jolly <paul@myitcv.io>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org
Subject: Re: Automatically re-running commands during an interactive rebase or post commit
Date: Mon, 29 May 2023 15:01:50 +0100	[thread overview]
Message-ID: <CACoUkn6wzoHph+BU3eYWqmf4ZWGji08Qhhjn+z4zrWJp1csPbQ@mail.gmail.com> (raw)
In-Reply-To: <002901d99233$3d0c8b80$b725a280$@nexbridge.com>

> >Please can someone help nudge me in the right direction?
>
> I wonder whether setting up a clean/smudge filter might help. You might want to look into a clean filter that runs your code generator.

Thanks. I'm not clear that this will help, because the main problem is
that the rebase stops when trying to apply a later commit. In this
case, the previous commit will be "clean", but the commit the rebase
is trying to apply will conflict and the rebase process will stop

Reading elsewhere, I'm now looking into whether wrapping the default
mergetool will help provide the "hooks" I need.

  reply	other threads:[~2023-05-29 14:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 13:38 Automatically re-running commands during an interactive rebase or post commit Paul Jolly
2023-05-29 13:41 ` rsbecker
2023-05-29 14:01   ` Paul Jolly [this message]
2023-05-29 16:02 ` Paul Jolly
2023-05-29 17:53   ` Phillip Wood
2023-05-29 19:08     ` Paul Jolly
2023-05-29 19:48       ` Phillip Wood
2023-05-31  4:14         ` Elijah Newren
2023-06-02  9:57           ` Phillip Wood
2023-06-08  5:11           ` Paul Jolly
2023-05-30  7:22 ` Son Luong Ngoc
2023-05-30  9:44 ` Oswald Buddenhagen
2023-05-30 10:27   ` Paul Jolly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACoUkn6wzoHph+BU3eYWqmf4ZWGji08Qhhjn+z4zrWJp1csPbQ@mail.gmail.com \
    --to=paul@myitcv.io \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).