From ed5df2b0f37a153681beec91cdd9a71663f3a0bc Mon Sep 17 00:00:00 2001 From: Richard Jenkins Date: Mon, 29 May 2017 22:04:58 +0100 Subject: [PATCH] +[ci skip] info --- Commit-Messages.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Commit-Messages.md b/Commit-Messages.md index 160cf9f..2a2f817 100644 --- a/Commit-Messages.md +++ b/Commit-Messages.md @@ -38,9 +38,12 @@ Number of sold items was being overwritten by a memmove on the field before it. Queue time changed to only be drawn for rides. ``` -**Notes** +### **Text-only commits** +If you are **only** making a change to text files (e.g. the changelog), please put `[ci skip]` as the body of the commit message. This tells the continuous integration systems not to process the commit - CI isn't needed for changes that don't touch the code. + +### **Notes** * A commit message should say what the change **includes** and **why**. * The summary should start with a verb in the present tense (e.g. Add, change, fix etc.). -* If the first line of commit message is over 72 characters, GitHub's UI will fold it. +* 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. \ No newline at end of file