From 733e04a2b18055df2ef67a725b0c160011842ea8 Mon Sep 17 00:00:00 2001 From: BeFunes Date: Mon, 22 Sep 2025 22:52:27 +0200 Subject: [PATCH] Update skip-build.adoc --- docs/guides/modules/orchestrate/pages/skip-build.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/modules/orchestrate/pages/skip-build.adoc b/docs/guides/modules/orchestrate/pages/skip-build.adoc index 30fef8293a..ff60750990 100644 --- a/docs/guides/modules/orchestrate/pages/skip-build.adoc +++ b/docs/guides/modules/orchestrate/pages/skip-build.adoc @@ -34,7 +34,7 @@ A few points to note regarding the scope of the `ci skip` feature: * If you push multiple commits at once, and the latest commit includes a `[ci skip]` or `[skip ci]` tag, it will skip the pipeline execution for all commits in that push. * This feature is not supported for fork PRs. Scheduled workflows will run even if you push a commit with `[ci skip]` message. Changing the config file is the way to upgrade the current schedule. * For GitHub OAuth and Bitbucket Cloud pipelines, this functionality applies also when the pipeline is triggered via API, manually via the web app, or via schedule. -* GitHub App pipelines triggered via Custom webhook or via schedule are never skipped +* GitHub App pipelines triggered via custom webhook, schedule, API or manually via the web-app are never skipped === Example commit title