diff options
| author | Stan Hu <stanhu@gmail.com> | 2015-10-23 20:36:55 +0300 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2015-10-23 20:36:55 +0300 |
| commit | ceaf8b73a35748afbb2e217c1c015103090015a3 (patch) | |
| tree | 14933e31d0fd9ce03fc15b306d91a6201c130cd3 | |
| parent | 0bb50ea081e6817e6d67c4f1dbe08f3d2fd720e1 (diff) | |
| parent | b2663d1ca171c62435c292481ff5b45eb4230f4b (diff) | |
Merge pull request #9765 from drobati/patch-1
Added missing period in gitlab_flow article.
| -rw-r--r-- | doc/workflow/gitlab_flow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md index f608674faf6..9a24a1e252a 100644 --- a/doc/workflow/gitlab_flow.md +++ b/doc/workflow/gitlab_flow.md @@ -26,7 +26,7 @@ After getting used to these three steps the branching model becomes the challeng Since many organizations new to git have no conventions how to work with it, it can quickly become a mess. The biggest problem they run into is that many long running branches that each contain part of the changes are around. People have a hard time figuring out which branch they should develop on or deploy to production. -Frequently the reaction to this problem is to adopt a standardized pattern such as [git flow](http://nvie.com/posts/a-successful-git-branching-model/) and [GitHub flow](http://scottchacon.com/2011/08/31/github-flow.html) +Frequently the reaction to this problem is to adopt a standardized pattern such as [git flow](http://nvie.com/posts/a-successful-git-branching-model/) and [GitHub flow](http://scottchacon.com/2011/08/31/github-flow.html). We think there is still room for improvement and will detail a set of practices we call GitLab flow. ## Git flow and its problems |