Skip to content
MyTwigMyTwigMyTwig Docs

Bisect and the command log

Bisect

Section titled “Bisect”

Bisect finds the first bad commit by testing the commits in between, halving the range each time.

  1. Start it from a commit’s menu with Start Bisect: This Commit Is Bad, or pick two commits and choose Bisect Between the 2 Commits (the newer one is bad).
  2. A banner over the graph names the commit checked out for you to test, how many are left, and roughly how many steps.
  3. Test it, then click Good, Bad or Skip.
  4. When Git finds the first bad commit, the banner names it and the graph selects it.
  5. Reset checks out what you had before.

The graph marks the commits you’ve marked good, bad and skipped. The palette has every bisect action too.

Git command log

Section titled “Git command log”

View → Git Command Log lists the last 1,000 Git commands MyTwig ran, newest first: the arguments, the repository, how long each took, its exit status and what it printed to stderr. Credentials in URLs, authorization headers and tokens are hidden.

Tick the box to show only the open repository’s commands. Right-click an entry to copy its command line, or Copy All to copy the log. This is useful when something didn’t go as expected, or to learn the Git command behind a button.