Skip to content
Snippets Groups Projects
Verified Commit 89c460fa authored by Suzanne Selhorn's avatar Suzanne Selhorn Committed by GitLab
Browse files

Clarifying that we still validate history with Ruby

parent ab1d27b5
No related branches found
No related tags found
2 merge requests!144312Change service start (cut-off) date for code suggestions to March 15th,!143252Clarifying that we still validate history with Ruby
......@@ -42,19 +42,22 @@ For example:
This feature does something.
```
The item text should include these words in order. Capitalization doesn't matter.
The item text must include these words in order. Capitalization doesn't matter.
- `introduced`, `enabled`, `deprecated`, `changed`, `moved`, `recommended`, `removed`, or `renamed`
- `in` or `to`
- `GitLab` (or, for external projects, the name of the project)
If you cannot use this format, you can use different language. Try to be
consistent with other notes on the page, or other notes on the docs site.
The docs site uses [Ruby code](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/lib/filters/introduced_in.rb)
to render the notes based on these words.
If possible, include a link to the related issue, merge request, or epic.
Do not link to the pricing page. Do not include the subscription tier.
In addition:
Even if you have only one item, ensure it begins with `> -`.
- Try to be consistent with other notes on the page, or other notes on the docs site.
- Ensure that the output generates properly.
- If possible, include a link to the related issue, merge request, or epic.
- Do not link to the pricing page. Do not include the subscription tier.
- Even if you have only one item, ensure it begins with `> -`.
#### Introducing a new feature
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment