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

Feature request - optionally include merge conflicts in `git add -p`

From
JWJarrad Whitaker <jarrad.whitaker@gmail.com>
Date
May 27, 2025, 23:54 UTC
Message-ID
<CAOWMAxwQacT=PcPrWiuEJzSH24ELDBxq2XMNX1X75KSp6cS6jw@mail.gmail.com>
Hey all,

A small feature request (and hopefully not a small "tell me I misread the docs"!) -

When fixing up conflicts from a rebase / cherry-pick / etc, files with conflicts are excluded from `git add`. This is very sensible in almost all cases.

However, would it make sense to make a special case for `git add -p` / `git add --patch` / patch mode of `git add --interactive`? There seems no reason to exclude potentially unmerged files in mode, which goes through changes chunk by chunk.

Excluding these files means I need to manually go copy paste the filename into `git add` (the horror), and additionally I don't get the great chunk-by-chunk feedback from patch mode above.

Cheers! Jarrad

Next: Chris Torek
Message 1 of 3 in “Feature request - optionally include merge conflicts in `git add -p`”
  1. Jarrad WhitakerMay 27, 2025
  2. Chris TorekMay 28, 2025
  3. Jarrad WhitakerMay 31, 2025

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.