Skip to content

Latest commit

 

History

History
21 lines (16 loc) · 782 Bytes

README.md

File metadata and controls

21 lines (16 loc) · 782 Bytes

UI-Kit Bisect

A tool to find out where bugs come from in ui-kit

How to use?

  1. Create a branch
  2. Write a test that fails on the first commit you know where the issue is.
  1. Leap in the past and find a commit where the test do pass.
  2. Commit your test into your branch
  3. Go to the workflow and run it with:
    • Use workflow from yourBranch
    • The latest known good commit
    • The latest known bad commit
  4. Go grab some coffee
  5. Check the logs, the commit introducing the issue should've been found!

How does it work?

See git bisect examples