From 7b292590cd6aebf2a7afd1eec924f4ff6e531c70 Mon Sep 17 00:00:00 2001 From: Margen67 Date: Tue, 20 Apr 2021 12:31:43 -1000 Subject: [PATCH] Updated Commit Messages (markdown) --- Commit-Messages.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Commit-Messages.md b/Commit-Messages.md index 5fdbeae..6971b8c 100644 --- a/Commit-Messages.md +++ b/Commit-Messages.md @@ -25,12 +25,10 @@ Further paragraphs come after blank lines. - Use a hanging indent ``` - **Bug Fix:** Remember that each commit has to be understandable on its own, without having to cross-reference GitHub. A commit message like `Fix #1234` is not acceptable. - ``` Fix #3107: Number of sold items is reset after some time @@ -44,4 +42,4 @@ before it. Queue time changed to only be drawn for rides. * If the first line of commit message is over 72 characters, GitHub's UI will fold it. Please keep the first line below this limit. * There has to be one line of space between the topic (first line) and body of commitmsg * If you cannot fit the description and your commit is large, consider splitting it into smaller chunks. -* As of https://github.com/OpenRCT2/OpenRCT2/pull/11410 at least the basic commit message style will be enforced by CI \ No newline at end of file +* As of [#11410](https://github.com/OpenRCT2/OpenRCT2/pull/11410) at least the basic commit message style will be enforced by CI.