Conversation

Notices

1. Hypolite Petovan (hypolite@friendica.mrpetovan.com)'s status on Tuesday, 19-Dec-2017 00:09:30 EST Hypolite Petovan
   Random git awesomeness: git-bisect
   
   Something in your versioned project suddenly broke and you have no specific idea when the breaking change was introduced? Fear not, here's git-bisect!
   
   This helpful tool checks out a revision between the current branch and the provided last known working revision. It lets you test for the faulty behavior, then tell it whether it was working or not at this point in time. Git will then check out a new revision between two new boundaries depending on the previous input. After about 2log(N) steps where N is the total number of commits between the current branch and the last known working revision, it will then present you with the first commit where it all went down.
   
   This tool is especially useful in open source projects with many moving parts and few automatic regression tests. Pro Tip: you can use the date the faulty behavior was first reported to cull down the number of revisions Git will have to wade through, although the binary search is pretty well-suited to big datasets.
   
   Thanks to @Michael Vogel for the discovery! https://git-scm.com/docs/git-bisect #opensource #versioning #git
   1. Michael Vogel (heluecht@pirati.ca)'s status on Tuesday, 19-Dec-2017 00:47:55 EST Michael Vogel

      in reply to
      I heard about it from @Tobias
      1. Tobias (tobias@social.diekershoff.de)'s status on Tuesday, 19-Dec-2017 02:07:22 EST Tobias

         in reply to
         Just passing along the wisdom of Master @Fabio 🎄
         1. Hypolite Petovan (hypolite@friendica.mrpetovan.com)'s status on Tuesday, 19-Dec-2017 08:26:26 EST Hypolite Petovan

            in reply to
            Thanks @Fabio 🎄 !