summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-11-13 12:06:22 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-11-13 12:06:22 +0000
commit4e516dbff9767a35677fdc4a6e39005b4b564376 (patch)
tree7c650b30777b8e7f72cafb186e9446a50d3fa3be /PROCESS.md
parent4f01ac5ba0bf72427ed4fef9b229d056dbb60e89 (diff)
downloadgitlab-ce-4e516dbff9767a35677fdc4a6e39005b4b564376.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 6bff60bff0f..45f28b33a63 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -79,7 +79,7 @@ star, smile, etc.). Some good tips about code reviews can be found in our
Overview and details of feature flag processes in development of GitLab itself is described in [feature flags process documentation](https://docs.gitlab.com/ee/development/feature_flags/process.html).
-Guides on how to include feature flags in your backend/frontend code while developing GitLab are described in [developing with feature flags documentation](https://docs.gitlab.com/ee/development/feature_flags/developing.html).
+Guides on how to include feature flags in your backend/frontend code while developing GitLab are described in [developing with feature flags documentation](https://docs.gitlab.com/ee/development/feature_flags/development.html).
Getting access and how to expose the feature to users is detailed in [controlling feature flags documentation](https://docs.gitlab.com/ee/development/feature_flags/controls.html).