Clarify that changelog entries end with a full stop
This commit is contained in:
parent
fcc26d247e
commit
5f12419afb
2 changed files with 4 additions and 4 deletions
|
@ -99,7 +99,7 @@ the ``newsfragments`` directory. The ``type`` can be one of the following:
|
||||||
* ``deprecation`` - Used when deprecating something
|
* ``deprecation`` - Used when deprecating something
|
||||||
|
|
||||||
All news fragments must have a brief summary explaining the change in the contents
|
All news fragments must have a brief summary explaining the change in the contents
|
||||||
of the file.
|
of the file. The summary must end in a full stop to be in line with the style guide.
|
||||||
|
|
||||||
Changes that do not change the spec, such as changes to the build script, formatting,
|
Changes that do not change the spec, such as changes to the build script, formatting,
|
||||||
CSS, etc should not get a news fragment.
|
CSS, etc should not get a news fragment.
|
||||||
|
|
|
@ -1 +1 @@
|
||||||
Add missing status_msg to m.presence schema
|
Add missing status_msg to m.presence schema.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue