News for hackers. Stuff that matters.

A comment on Squash your commits. Parent comment

Re:Squash your commits by hinkley on Friday April 01, 2016 @07:14PM (#11409241)
Anything not stored on the system of record cannot be counted on to exist at any point in the future.

From a strategic standpoint, thinking of that data as anything other than 'destroyed' would be a grave error of judgement. From a retention standpoint the difference between 'could' and 'did' is profound.

[ Parent | on HN ]
Re:Squash your commits by jasonlotito on Friday April 01, 2016 @10:44PM (#11409988)
> Anything not stored on the system of record cannot be counted on to exist at any point in the future.

That's an issue with GitHub itself, not an issue with the method of squashing commits before merging into master. See gerrit as a prime example of separating reviewing code and your master branch.

[ Parent | on HN ]
Re:Squash your commits by cdcarter on Saturday April 02, 2016 @01:36AM (#11410393)
If you have an issue with people deleting branches that were intentionally preserved to save history that was then squashed onto master, that's not the fault of anyone who squashed their commits but left them preserved on a branch.
[ Parent | on HN ]