summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbart <bart.kranstauber@ieu.uzh.ch>2017-07-28 13:28:47 +0000
committerbart <bart.kranstauber@ieu.uzh.ch>2017-07-28 13:28:47 +0000
commit329391ced723a62b20d0ce9bb4746e0f4074f395 (patch)
tree97f33f4d92add72b1c98dba7bdc3e29f358997bf
parent48c51e207e4cba8a69e4ca65cba1e169d384cefa (diff)
downloadgitlab-ce-329391ced723a62b20d0ce9bb4746e0f4074f395.tar.gz
Update gitlab_flow.md, Teatro seems to be completely dead, see also https://forum.gitlab.com/t/gitlab-flow-documentation-teatro/7774
-rw-r--r--doc/workflow/gitlab_flow.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md
index ea28968fbb2..9d466ae1971 100644
--- a/doc/workflow/gitlab_flow.md
+++ b/doc/workflow/gitlab_flow.md
@@ -91,7 +91,6 @@ This workflow where commits only flow downstream ensures that everything has bee
If you need to cherry-pick a commit with a hotfix it is common to develop it on a feature branch and merge it into master with a merge request, do not delete the feature branch.
If master is good to go (it should be if you are practicing [continuous delivery](http://martinfowler.com/bliki/ContinuousDelivery.html)) you then merge it to the other branches.
If this is not possible because more manual testing is required you can send merge requests from the feature branch to the downstream branches.
-An 'extreme' version of environment branches are setting up an environment for each feature branch as done by [Teatro](https://teatro.io/).
## Release branches with GitLab flow