[TASK] Remove Commit Messages conventions

We do not have strict rules for commit messages. Where necessary we can refer to core rules, but we do not need to repeat them here.
TYPO3-Documentation · Jan 30, 2024 · c79b975 · c79b975
1 parent 4437f39
commit c79b975
Show file tree

Hide file tree

Showing 5 changed files with 1 addition and 135 deletions.
diff --git a/Documentation/GeneralConventions/CommitMessages.rst b/Documentation/GeneralConventions/CommitMessages.rst
diff --git a/Documentation/GeneralConventions/Index.rst b/Documentation/GeneralConventions/Index.rst
@@ -103,5 +103,4 @@ be found in the subchapters.
     Format
     CodingGuidelines
     GuidelinesForImages
-    CommitMessages
     Licenses
diff --git a/Documentation/Maintainers/BackportChanges.rst b/Documentation/Maintainers/BackportChanges.rst
@@ -10,8 +10,7 @@ Backport changes
 Most of the time changes will be made to branch `main` and backported.
 
 When creating a pull request, it is possible to add a `Releases` line in the
-:ref:`commit message <general-conventions-commit-messages>`
-(as done in the Core):
+commit message (as done in the Core):
 
 ..  code-block:: text
 

diff --git a/Documentation/Maintainers/Changelog.rst b/Documentation/Maintainers/Changelog.rst
@@ -37,8 +37,6 @@ their commit message to the issue, for example
     Resolves: https://github.com/TYPO3-Documentation/Changelog-To-Doc/issues/790
     Releases: main
 
-See also: :ref:`general-conventions-commit-messages`.
-
 ..  index::
     Documentation; Deprecations
     reST directives; deprecated

diff --git a/Documentation/WritingDocsOfficial/LocalEditing.rst b/Documentation/WritingDocsOfficial/LocalEditing.rst
@@ -98,8 +98,6 @@ the ability to experiment and preview your changes locally before submitting the
       git commit -a
 
    Write a short, meaningful commit message describing what changes you have made.
-   See :ref:`general-conventions-commit-messages` for more information on how to
-   word your commit messages.
 
 9. Push changes