AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
daniel.motzko
2021-06-30 13:54:36 +02:00
parent 0b81d0318c
commit 86e42178df
16 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
radar/2019-11-01/gitflow.md
View File

@@ -6,9 +6,9 @@ quadrant: methods-and-patterns
---
Ever since there are recurring discussions about the version control strategy that a team should use.
We have also made the experience when new teams start off with using blocking or long lived feature branches (merge late once all review comments are done) it has a negative impact on team performance.
We have also made the experience when new teams start off with using blocking or long-lived feature branches (merge late once all review comments are done) it has a negative impact on team performance.
We recommend to use trunk based development with short lived (<1day) feature branches, because this has shown to support continuous integration and team collaboration the best. However we do accept teams choices to use GitFlow, we just do not try to encourage them in the first place.
We recommend to use trunk based development with short-lived (<1day) feature branches, because this has shown to support continuous integration and team collaboration the best. However, we do accept teams choices to use GitFlow, we just do not try to encourage them in the first place.
See also:
* trunk based development https://trunkbaseddevelopment.com/