docs: put performance improvements alongside code changes

apiaryio · Apr 8, 2019 · ab541b0 · ab541b0
1 parent b193f1a
commit ab541b0
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/internals.rst b/docs/internals.rst
@@ -69,11 +69,11 @@ Where ``<type>`` is a prefix, which tells Semantic Release what kind of changes
 -  ``feat`` - New functionality added (results in _minor_ version bump)
 -  ``fix`` - Broken functionality fixed (results in _patch_ version bump)
 -  ``refactor`` - Changes in code, but no changes in behavior
+-  ``perf`` - Performance improved
 -  ``style`` - Changes in code formatting
 -  ``test`` - Changes in tests
 -  ``docs`` - Changes in documentation
 -  ``chore`` - Changes in package or repository configuration
--  ``perf`` - Performance improved
 
 In the rare cases when your changes break backwards compatibility, the message must include ``BREAKING CHANGE:``, followed by an explanation. That will result in bumping the major version.