Hi, Following "popular request", we are happy to announce that users can now request to skip Linaro CI precommit testing for some patches.
The current implementation skips testing in two cases: 1- there is [RFC] or [RFC v[0-9]] in the patch subject 2- the commit message contains a line starting with 'CI-tag: skip' [1] Enables to avoid undesirable regression notifications when one sends an incomplete patch to start discussing ideas. [2] Aims at helping workflows where people submit patches for "master files" and "regenerated files" as two patches to make review easier. In such cases, the patch with only "master files" changes would generally generate regression notifications, confusing both reviewers and patch authors. For instance: - patch #1/3: introduce new code -> should pass CI - patch #2/3: changes to "master files" -> skip CI - patch #3/3: changes to "regenerated files" -> should pass CI This change does NOT affect postcommit CI, where CI is always expected to pass (otherwise regression notifications will be generated). Technically, we use 'git am --keep' when applying the patches, so that subject lines are untouched: this enables us to handle standard markers such as [PATCH RFC] or [RFC PATCH] for instance. This also means that a 'CI-tag: skip' after the usual '---' lines will be ignored (git-am will consider it as part of the patch, rather than the commit message). People used to git am --scissors may find it convenient to put the tag at the start of the commit message: ==================== CI-tag: skip -- >8 -- ===================== But it's fine to put that tag along with other tags (such as Signed-Off-By, Co-authored-by, ...) We hope this will be useful / helpful. Thanks, The Linaro Toolchain team.
