Add topic "Squash merge" Accepted
Changes: 4
-
Add Two years of squash merge - DNSimple Blog
- Title
-
- Unchanged
- Two years of squash merge - DNSimple Blog
- Type
-
- Unchanged
- Blog post
- Created
-
- Unchanged
- 2019-01-24
- Description
-
- Unchanged
- A retrospective of the last two years where we adopted --squash as our default merge strategy for git branches. A little more than two years ago, we decided to change the development team's workflow to always use git --squash merge. In this post I will highlight the reasons for this decision, how it worked for us, and what the benefits are.
- Link
-
- Unchanged
- https://blog.dnsimple.com/2019/01/two-years-of-squash-merge/
- Identifier
-
- Unchanged
- no value
Resource | v1 | current (v1) -
Add Squash merge
- Title
-
- Unchanged
- Squash merge
- Description
-
- Unchanged
- Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge takes all the file changes and adds them to a single new commit on the default branch.
- Link
-
- Unchanged
- https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash
Topic | v1 | current (v1) -
Add Squash merge cons given in Two years of squash merge - DNSimple Blog
- Current
- cons given in
Topic to resource relation | v1 -
Add Git parent of Squash merge
- Current
- parent of
Topic to topic relation | v1