Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
8ec4f9da
Commit
8ec4f9da
authored
Mar 11, 2021
by
Suzanne Selhorn
Committed by
Craig Norris
Mar 11, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added details about words the version bullet must include
parent
58680c45
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
5 deletions
+6
-5
doc/development/documentation/styleguide/index.md
doc/development/documentation/styleguide/index.md
+6
-5
No files found.
doc/development/documentation/styleguide/index.md
View file @
8ec4f9da
...
@@ -1611,11 +1611,12 @@ If all content in a section is related, add version text after the header for
...
@@ -1611,11 +1611,12 @@ If all content in a section is related, add version text after the header for
the section. The version information must:
the section. The version information must:
-
Be surrounded by blank lines.
-
Be surrounded by blank lines.
-
Start with
`>`
.
-
Start with
`>`
. If there are multiple bullets, each line must start with
`> -`
.
-
Version histories with more than one entry should have each entry on its own
-
The string must include these words in this order (capitalization doesn't matter):
line (long lines are okay). Start each line with
`> -`
to get unordered list
-
`introduced`
,
`deprecated`
,
`moved`
formatting.
-
`in`
or
`to`
-
Whenever possible, have a link to the completed issue, merge request, or epic
-
`GitLab`
-
Whenever possible, include a link to the completed issue, merge request, or epic
that introduced the feature. An issue is preferred over a merge request, and
that introduced the feature. An issue is preferred over a merge request, and
a merge request is preferred over an epic.
a merge request is preferred over an epic.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment