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

How to show "bisect" refs in "git log"?

From
BMBrendan McDonnell <bmcdonnell.emb@gmail.com>
Date
Jun 26, 2025, 17:58 UTC
Message-ID
<CA+MGQRBjx2XfhFo6Bs+X_WzRq9kB-ucZtTuw_kAfuZCVKGVvsw@mail.gmail.com>
I use this command
  git log --all --graph --decorate --pretty=oneline --abbrev-commit
frequently to visualize a repo's commit history.

It used to include "bisect" references in the output, until ~a couple years ago IIRC. Is there a way I can modify this command so that it includes them again, without excluding any references that it already includes? (Appending "--decorate-refs=refs/*" includes the bisect refs, but excludes some others that are there without it.)

Is this behavior change a bug, or intentional?
 - If intentional, why? And is it documented anywhere?
 - If it's a bug, should I report it somewhere (else)?
Thanks,
Brendan
Next: Jeff King
Message 1 of 2 in “How to show "bisect" refs in "git log"?”
  1. Brendan McDonnellJun 26, 2025
  2. Jeff KingJun 26, 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.