Commit fbe1c83b authored by Suzanne Selhorn's avatar Suzanne Selhorn

Merge branch 'msj-version-words-styleguide' into 'master'

Mention all words supported by version formatter

See merge request gitlab-org/gitlab!65067
parents bb600be2 991d471c
...@@ -750,7 +750,7 @@ For example: ...@@ -750,7 +750,7 @@ For example:
| App name | Description | | App name | Description |
|:---------|:---------------------------------| |:---------|:---------------------------------|
| App A | Description text. <sup>1</sup> | | App A | Description text. <sup>1</sup> |
| App B | Description text. <sup>2</sup> | | App B | Description text. <sup>2</sup> |
1. This is the footnote. 1. This is the footnote.
1. This is the other footnote. 1. This is the other footnote.
...@@ -1531,7 +1531,8 @@ the section. The version information must: ...@@ -1531,7 +1531,8 @@ the section. The version information must:
- Be surrounded by blank lines. - Be surrounded by blank lines.
- Start with `>`. If there are multiple bullets, each line must start with `> -`. - Start with `>`. If there are multiple bullets, each line must start with `> -`.
- The string must include these words in this order (capitalization doesn't matter): - The string must include these words in this order (capitalization doesn't matter):
- `introduced`, `deprecated`, `moved` - `introduced`, `deprecated`, `moved`, `recommended` (as in the
[feature flag documentation](../feature_flags.md)), `removed`, or `renamed`
- `in` or `to` - `in` or `to`
- `GitLab` - `GitLab`
- Whenever possible, include a link to the completed issue, merge request, or epic - Whenever possible, include a link to the completed issue, merge request, or epic
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment