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

Re: Automatically re-running commands during an interactive rebase or post commit

From
Paul Jolly <paul@myitcv.io>
Date
May 29, 2023, 14:01 UTC
Message-ID
<CACoUkn6wzoHph+BU3eYWqmf4ZWGji08Qhhjn+z4zrWJp1csPbQ@mail.gmail.com>
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.

Previous: rsbecker@nexbridge.comNext: Paul Jolly
Message 3 of 13 in “Automatically re-running commands during an interactive rebase or post commit”
  1. Paul JollyMay 29, 2023
  2. rsbecker@nexbridge.comMay 29, 2023
  3. Paul JollyMay 29, 2023
  4. Paul JollyMay 29, 2023
  5. Phillip WoodMay 29, 2023
  6. Paul JollyMay 29, 2023
  7. Phillip WoodMay 29, 2023
  8. Elijah NewrenMay 31, 2023
  9. Phillip WoodJun 2, 2023
  10. Paul JollyJun 8, 2023
  11. Son Luong NgocMay 30, 2023
  12. Oswald BuddenhagenMay 30, 2023
  13. Paul JollyMay 30, 2023

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.