diff options
author | Evan Read <eread@gitlab.com> | 2019-06-24 16:43:35 +1000 |
---|---|---|
committer | Evan Read <eread@gitlab.com> | 2019-06-25 09:22:39 +1000 |
commit | 4a8d256274b9f3e719c70933becf3ec7ec6d5c6c (patch) | |
tree | f1d5cee0ba8cf518aac840f898eae93a07ace69d /doc/user/group/index.md | |
parent | db9783f7826ed5ba58a8941dd80a1cd7dda517b0 (diff) | |
download | gitlab-ce-4a8d256274b9f3e719c70933becf3ec7ec6d5c6c.tar.gz |
Add Markdown lintingdocs/add-mdl-and-rule-032
Also adds and one linting rule
and makes project conform to it.
Diffstat (limited to 'doc/user/group/index.md')
-rw-r--r-- | doc/user/group/index.md | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 4fde45da6c4..183b12b1c73 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -41,12 +41,13 @@ You can create groups for numerous reasons. To name a couple: - Make it easier to `@mention` all of your team at once in issues and merge requests by creating a group and including the appropriate members. For example, you could create a group for your company members, and create a [subgroup](subgroups/index.md) for each individual team. Let's say you create a group called `company-team`, and you create subgroups in this group for the individual teams `backend-team`, `frontend-team`, and `production-team`. - - When you start a new implementation from an issue, you add a comment: - _"`@company-team`, let's do it! `@company-team/backend-team` you're good to go!"_ - - When your backend team needs help from frontend, they add a comment: - _"`@company-team/frontend-team` could you help us here please?"_ - - When the frontend team completes their implementation, they comment: - _"`@company-team/backend-team`, it's done! Let's ship it `@company-team/production-team`!"_ + +- When you start a new implementation from an issue, you add a comment: + _"`@company-team`, let's do it! `@company-team/backend-team` you're good to go!"_ +- When your backend team needs help from frontend, they add a comment: + _"`@company-team/frontend-team` could you help us here please?"_ +- When the frontend team completes their implementation, they comment: + _"`@company-team/backend-team`, it's done! Let's ship it `@company-team/production-team`!"_ ## Namespaces |