Git Bisect : débusquer rapidement l’origine d’un bug • Delicious Insights
▻https://delicious-insights.com/fr/articles/git-bisect
Exemple d’utilisation de git bisect
Voir aussi la doc officielle : ►https://git-scm.com/docs/git-bisect
Git Bisect : débusquer rapidement l’origine d’un bug • Delicious Insights
▻https://delicious-insights.com/fr/articles/git-bisect
Exemple d’utilisation de git bisect
Voir aussi la doc officielle : ►https://git-scm.com/docs/git-bisect
Understanding #git-bisect, i.e. Use Binary Search to Find the Change that Introduced a Bug
▻https://hackernoon.com/understanding-git-bisect-i-e-use-binary-search-to-find-the-change-that-i
Git is a powerful tool. Once you’ve mastered commit and merge, there are endless possibilities. A very useful one is #git-bisect. It helps you find a commit that introduced a certain change in behavior.▻https://medium.com/media/3fb729766df385f7ee136118b5d00bfb/hrefWhen you find a regression, something broken that used to work, use git-bisect to find the commit that broke it. Mark the current commit as bad and mark an old commit, where that feature still worked, as good. Git-bisect will then #bisect all the changes between those two commits with a binary search. At every step, you are asked to mark the commit as good or bad until bisect finds the first bad commit.How to use git-bisectgit bisect startnpm test # Double check that this commit is broken.git bisect badgit log —oneline # (...)
Infinoid/svn-bisect · GitHub
▻https://github.com/Infinoid/svn-bisect
This is a command-line tool inspired by “#git-#bisect”, which allows you to
perform binary searches among the revisions of a subversion project.
There’s lots of documentation in the “#svn-#bisect” file. Author, usage,
screenshot, license, it’s all in there. Please run “perldoc svn-bisect” to
read it. If you don’t have a “perldoc” command, you can just open it in your
favorite pager or text editor, or maybe even your web browser. Or, if it has
been installed properly, you could try “svn-bisect help”.