News for hackers. Stuff that matters.

A comment on Git: Using Advanced Rebase Features for a Clean Repository. Parent comment

Re:Git: Using Advanced Rebase Features for a Clean Repository by jeff_vader on Wednesday August 09, 2017 @07:41AM (#14967573)
Say we work together. Why would you want to see my 5 solutions to a problem in `master`, of which 4 actually never really ran in production? I do commit often, things that I try and later throw away are in the history. Once rebased and squashed, only final solution is in `master` history.
[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by chii on Wednesday August 09, 2017 @08:07AM (#14967727)
> 4 actually never really ran in production?

but the history showed that it was tried (and perhaps the commit message can have a short note on why it wasn't selected).

without the git history, you'd have to rely on human memory to know this. Or a separately maintained documentation (which, lets face it, is never going to get updated).

[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by Tade0 on Wednesday August 09, 2017 @08:59AM (#14968225)
Or store it in another branch - that's the approach we had been using in one company I worked at.
[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by radiospiel on Wednesday August 09, 2017 @02:56PM (#14972441)
Ah, yes, this was implied :) only working code (as checked via CI) is allowed to show up in master and other long living branches.
[ Parent | on HN ]
Re:Git: Using Advanced Rebase Features for a Clean Repository by branja on Wednesday August 09, 2017 @08:06AM (#14967721)
This is much easier when I actually need to trawl through history to find things.
[ Parent | on HN ]