Re:Squash your commits
by sulam on Friday April 01, 2016 @05:56PM
(#11408897)
It's not destroyed, it's simply not on master. If you want to push that branch and have the history forever, that is an option.
[ Parent
| on HN ]
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.
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.
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.