Commit ed917e36 authored by Mike Lewis's avatar Mike Lewis

Improve language/policy on standard for merging

parent 92e5e4c1
...@@ -259,13 +259,12 @@ Before getting started, make sure you read the introductory section ...@@ -259,13 +259,12 @@ Before getting started, make sure you read the introductory section
- Label the MR `Documentation` - Label the MR `Documentation`
- Assign the correct milestone (see note below) - Assign the correct milestone (see note below)
Documentation will be merged if it meets our style standards, is clear, and is known to be Documentation will be merged if it is an improvement on existing content,
correct by the person merging the MR or the SME (such as a developer) who contributed it. represents a good-faith effort to follow the template and style standards,
Further needs for ‘what would make this doc even better’ should be immediately addressed in a and is believed to be accurate.
follow-up MR or issue.
The individual who merges the documentation must reviewed the documentation Further needs for what would make the doc even better should be immediately addressed
for the above standard. in a follow-up MR or issue.
NOTE: **Note:** NOTE: **Note:**
If the release version you want to add the documentation to has already been If the release version you want to add the documentation to has already been
......
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