Re:Git is too hard
by jamienicol on Tuesday November 17, 2020 @09:36AM
(#25124145)
> The vast majority of people do not.
That's a very bold claim.
It's certainly been the expected workflow everywhere I've worked. You might consider it a waste of time but I'd wager the resulting mess of commits from not doing so wastes far more time in the long run.
I've never worked in an environment where it was expected or used. As far as I can tell, no time has been wasted as a result. How would it cause time wasting?
Re:Git is too hard
by jamienicol on Tuesday November 17, 2020 @10:17AM
(#25124676)
Without a clean history it takes longer to find which commit changed things and why.
I believe I've really only needed to do that once. git bisect handled it in about 10 minutes IIRC. It's hard for me to imagine how I could achieve a net time savings against that level of commit-hunting.
Re:Git is too hard
by jamienicol on Tuesday November 17, 2020 @11:44AM
(#25125861)
I envy you then. I spend a great deal of time looking through history to find bugs.
An unclean history is less likely to work well with bisect too, as the individual commits may be broken.
Re:Git is too hard
by Supermancho on Wednesday November 18, 2020 @12:14PM
(#25139394)
> I spend a great deal of time looking through history to find bugs.
You mean when where and how a change was introduced? I dont think bugs are located in the history, since bugs are operational failures on a deployed branch.
Re:Git is too hard
by jamienicol on Wednesday November 18, 2020 @07:03PM
(#25144435)
Yes, I phrased that badly. Let's say looking through history to understand the context of when bugs were introduced and how to fix them
> That's exactly what I'd expect someone to do after I commented on their PR.
The vast majority of people do not. I certainly wouldn't expect someone to waste time on that.