From 42a1d5e22bd0a287d664a7d443828274bac8f1f3 Mon Sep 17 00:00:00 2001 From: Gijs van Dam Date: Mon, 23 Sep 2024 14:17:54 +0200 Subject: [PATCH] docs: clarify skipping the CI checks [skip ci] --- docs/code_contribution_guidelines.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/code_contribution_guidelines.md b/docs/code_contribution_guidelines.md index a847b6fe9..62c7d889b 100644 --- a/docs/code_contribution_guidelines.md +++ b/docs/code_contribution_guidelines.md @@ -335,7 +335,10 @@ Examples of common patterns w.r.t commit structures within the project: codebase. * If a PR only fixes a trivial issue, such as updating documentation on a small scale, fix typos, or any changes that do not modify the code, the - commit message should end with `[skip ci]` to skip the CI checks. + commit message of the HEAD commit of the PR should end with `[skip ci]` to + skip the CI checks. When pushing to such an existing PR, the latest commit + being pushed should end with `[skip ci]` as to not inadvertantly trigger the + CI checks. ## Sign your git commits