summaryrefslogtreecommitdiff
path: root/doc/ci/environments.md
diff options
context:
space:
mode:
authorPhil Hughes <me@iamphill.com>2016-10-06 15:30:34 +0100
committerPhil Hughes <me@iamphill.com>2016-10-06 15:30:34 +0100
commit996e802415aa1edadb96b1f7efa924581fb047ed (patch)
tree316dd7319d2cc723b5c311f099065e9b4fdb11d6 /doc/ci/environments.md
parenta0eaff14124b829ccc02df951bd7cb7d3abb7708 (diff)
parentdcfda304aa8c06f427cb5672ceb4e070047436be (diff)
downloadgitlab-ce-996e802415aa1edadb96b1f7efa924581fb047ed.tar.gz
Merge branch 'master' into members-ui
Diffstat (limited to 'doc/ci/environments.md')
-rw-r--r--doc/ci/environments.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/ci/environments.md b/doc/ci/environments.md
index d85b8a34ced..e070302fb82 100644
--- a/doc/ci/environments.md
+++ b/doc/ci/environments.md
@@ -14,6 +14,19 @@ Defining environments in a project's `.gitlab-ci.yml` lets developers track
Deployments are created when [jobs] deploy versions of code to [environments].
+### Checkout deployments locally
+
+Since 8.13, a reference in the git repository is saved for each deployment. So
+knowing what the state is of your current environments is only a `git fetch`
+away.
+
+In your git config, append the `[remote "<your-remote>"]` block with an extra
+fetch line:
+
+```
+fetch = +refs/environments/*:refs/remotes/origin/environments/*
+```
+
## Defining environments
You can create and delete environments manually in the web interface, but we