[TASK] Remove Commit Messages conventions (#388)

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 · b29663d · b29663d
1 parent 41e6edc
commit b29663d
Show file tree

Hide file tree

Showing 5 changed files with 14 additions and 152 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
@@ -92,19 +92,15 @@ be found in the subchapters.
 
    This will look like this: :guilabel:`Admin Tools > Extensions`
 
-
-
-
-**Table of contents**
-
-.. toctree::
-   :maxdepth: 1
-
-   ContentStyleGuide
-   Glossary
-   FileStructure
-   Format
-   CodingGuidelines
-   GuidelinesForImages
-   CommitMessages
-   Licenses
+..  toctree::
+    :caption: Table of contents
+    :maxdepth: 1
+
+    ContentStyleGuide
+    Glossary
+    FileStructure
+    GuidesXml
+    Format
+    CodingGuidelines
+    GuidelinesForImages
+    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
@@ -102,10 +102,7 @@ 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
-    phrase your commit messages. Please also add links to resources which might be useful
-    for a reviewer to know (when appropriate).
+   Write a short, meaningful commit message describing what changes you have made.
 
 9.  Push changes