summaryrefslogtreecommitdiff
path: root/PROCESS.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-03-11 21:09:09 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-03-11 21:09:09 +0000
commit19d63dbca44d8380b8bc0d51d890137691ddf2a7 (patch)
tree534885124a1edfcf4c22f61b93f6f8d270e03ac3 /PROCESS.md
parent9d195600e6266da44917f08c622a21a6d4c2317b (diff)
downloadgitlab-ce-19d63dbca44d8380b8bc0d51d890137691ddf2a7.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'PROCESS.md')
-rw-r--r--PROCESS.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 820f19a290b..67abe2f0a98 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -77,9 +77,9 @@ star, smile, etc.). Some good tips about code reviews can be found in our
## Feature flags
-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).
+Overview and details of feature flag processes in development of GitLab itself is described in [feature flags process documentation](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/).
-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).
+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).
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).