Skip to content

Latest commit

 

History

History
executable file
·
21 lines (15 loc) · 517 Bytes

README.md

File metadata and controls

executable file
·
21 lines (15 loc) · 517 Bytes
Raw

gitkatas

Bad Commit

One of the commits on master introduced a bad file. Find the commit and revert it using bisect.

Setup:

  1. Run . setup.sh (or .\setup.ps1 in PowerShell)

Useful commands

  • git bisect start
  • git bisect bad
  • git bisect good <commit-ish>
  • git bisect good
  • git bisect reset
  • git bisect run <cmd>
  • test ! -f badfile (or gci . badfile in PowerShell) to test the existence of a file
  • test ! -f badfile;echo $? to output the result of the test to the console