News for hackers. Stuff that matters.
Re:Git Tricks: Avoiding merge when dealing with remote confl... by kazinator on Monday October 21, 2019 @08:46PM (#21319239)
That article is some FUD about a real bug in a feature branch being masked due to other bugs that were introduced by the rebase itself.

That is not realistic because, firstly, a very specific test can (and should) be used for git bisect. You're not just testing for "software fails", but "very specific case fails in a specific way".

If some intermediate issues prevent you from testing the specific test case (you're not able to call "good" or "bad"), you can tell git bisect to skip that commit.

Shit happens! Bug was introduced a month ago, but two weeks ago, a range of commits happened that don't even build in your environment. git bisect will hit that.

The article also glosses over the possibility that git bisect goes back farther than the bad commit. Commits that are not testable can occur earlier or later than the one we are looking for.

Basically the article is just a new version of the old meme "merging is dangerous". except that it doesn't make any sense, since both "git merge" and "git rebase" textually merge code.

There are no comments on this comment yet.