diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-02-18 12:45:46 +0300 |
| commit | a7b3560714b4d9cc4ab32dffcd1f74a284b93580 (patch) | |
| tree | 7452bd5c3545c2fa67a28aa013835fb4fa071baf /doc/development/directory_structure.md | |
| parent | ee9173579ae56a3dbfe5afe9f9410c65bb327ca7 (diff) | |
Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42
Diffstat (limited to 'doc/development/directory_structure.md')
| -rw-r--r-- | doc/development/directory_structure.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/directory_structure.md b/doc/development/directory_structure.md index 8ba77bade2c..f909fda897f 100644 --- a/doc/development/directory_structure.md +++ b/doc/development/directory_structure.md @@ -38,7 +38,7 @@ end ### About namespace naming A good guideline for naming a top-level namespace (bounded context) is to use the related -feature category. For example, `Continuous Integration` feature category maps to `Ci::` namespace. +[feature category](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/categories.yml). For example, `Continuous Integration` feature category maps to `Ci::` namespace. Alternatively a new class could be added to `Projects::` or `Groups::` if it's either: |