See "History Mutability" here: https://secure.phabricator.com/book/phabricator/article/arcanist_new_project/
Description
Description
Related Objects
Related Objects
- Mentioned In
- rMITK5251def0b26b: Merge branch 'T26452-DoNotSquash'
Event Timeline
Comment Actions
If we think about establishing a new Git Workflow, we might rethink this. It might be useful to have some mainline that only consists of squashed commits so each feature is represented by a single entry. However, the current scenario does neither force one or the other way to do it so we have both merge- and squash commits which makes it a bit arbitrary, in my opinion.