The value of a clean git history is often underestimated. I will explain one of the advantages based on the git bisect command.

  • danrot@kbin.socialOP
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    I agree that some stuff is easier when not squashing commits, but for the teams I’ve been working with I’ve felt that the pros of squashing outweigh the cons, but of course YMMV.

    But I didn’t know about git bisect skip, thanks for the tip! But sincere question: What happens if there are e.g. three adjacent broken commits? If I have skip all three of those and the error was introduced in one of them, then git cannot tell me which commit introduced the error, right?