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

Scriptable mode for git bisect

From
CFClaus Fischer <claus.fischer@clausfischer.com>
Date
Sep 23, 2022, 20:54 UTC
Message-ID
<Yy4c6/jHupgThj7j@clausfischer.com>
Dear Git maintainers,

I have looked at the manpage of git bisect but have not found what I need: I would like git bisect not just to report the 'bad' revision within a bunch of text but instead either stop at the first bad revision (the last good will then be HEAD~1) or report it in a scriptable way, i.e.

  BADHEAD=$(git bisect run --shut-up-and-report-the-bad)
Have I overlooked anything?
***

The pourpose is to keep the source trees of two different projects that share a few files synchronous. My good/bad-script is a script that checks whether these files are similar. I want git to stop at the first change in source tree A so that I can update source tree B with the same commit message, then proceed to the next change in A that changes one of those files.

Regards,
Cluas
Next: Đoàn Trần Công Danh
Message 1 of 8 in “Scriptable mode for git bisect”
  1. Claus FischerSep 23, 2022
  2. Đoàn Trần Công DanhSep 24, 2022
  3. Claus FischerSep 24, 2022
  4. Đoàn Trần Công DanhSep 24, 2022
  5. Junio C HamanoSep 24, 2022
  6. Đoàn Trần Công DanhSep 25, 2022
  7. Claus FischerSep 25, 2022
  8. Junio C HamanoSep 26, 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.