Update skip ci docs (#9525)

* Update skip-build.adoc

* Update skip-build.adoc

* Update skip-build.adoc

* Update skip-build.adoc

* Update skip-build.adoc

* Update skip-build.adoc

* Update skip-build.adoc

Author: BeFunes

docs/guides/modules/orchestrate/pages/skip-build.adoc

@@ -13,7 +13,7 @@ Both methods are described below.
 [#skip-jobs]
 == Skip CI for a specific push
 
-By default, CircleCI automatically triggers a pipeline whenever you push changes to your project. You can override this behavior by adding one of the following tags within the first 250 characters of the body or title of the **latest commit** you pushed:
+If you have a trigger configured to run a pipeline on push events to your repository, you can override this behavior by adding one of the following tags within the first 250 characters of the body or title of the **latest commit** you pushed:
 
 * `[ci skip]`
 * `[skip ci]`
@@ -33,6 +33,8 @@ 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
 
 === Example commit title