RHDEVDOCS-6412: Defining Cancel-In-Progress Enhancements for 1.19

Implementing SME review comments

RHDEVDOCS-6412: Incorporated peer review comments

Author: Dhruv-Soni11

modules/op-customizing-pipelines-as-code-configuration.adoc

@@ -48,5 +48,8 @@ To customize {pac}, cluster administrators can configure the following parameter
 
 | `secret-github-app-scope-extra-repos` | Additional repositories for scoping the generated GitHub access token. |
 
+| `enable-cancel-in-progress-on-pull-requests` | Automatically cancels in-progress pipeline runs for all pull requests when a new commit is added. This ensures the old pipeline run is cancelled only after the new one has successfully started. The `cancel-in-progress` annotation on individual runs still applies and overrides the global setting. | `false`
+
+| `enable-cancel-in-progress-on-push` | Automatically cancels in-progress pipeline runs for all push commits when a new commit is pushed. The old pipeline run is cancelled only after the new one has successfully started. The `cancel-in-progress` annotation on individual runs still applies and overrides this global setting. | `false`
 
 |===

modules/op-speccancel-pipeline-run-using-pipelines-as-code.adoc

@@ -26,10 +26,12 @@ annotations:
 # ...
 ----
 
+:FeatureName: Automatic cancellation-in-progress of pipeline runs
+include::snippets/technology-preview.adoc[]
+
 [NOTE]
 ====
-{pac} cancels a pipeline run _after_ starting a new copy of this pipeline run successfully. The `pipelinesascode.tekton.dev/cancel-in-progress` setting does _not_ ensure that only one copy of the pipeline run is executing at any time.
-====
+* {pac} cancels a pipeline run _after_ starting a new copy of this pipeline run successfully. The `pipelinesascode.tekton.dev/cancel-in-progress` setting does _not_ ensure that only one copy of the pipeline run is executing at any time.
 
-:FeatureName: Automatic cancellation-in-progress of pipeline runs
-include::snippets/technology-preview.adoc[]
+* To enable `cancellation-in-progress` for all default pipeline runs, use the `enable-cancel-in-progress-on-pull-requests` and the `enable-cancel-in-progress-on-push` settings. These settings are available in the `platforms.openshift.pipelinesAsCode.settings` spec of the `TektonConfig` custom resource (CR) configure {pac}. 
+====

pac/creating-pipeline-runs-pac.adoc

@@ -36,3 +36,9 @@ include::modules/op-filtering-pipeline-run-using-pipelines-as-code.adoc[leveloff
 * link:https://cel.dev/[Common Expression Language (CEL)]
 
 include::modules/op-speccancel-pipeline-run-using-pipelines-as-code.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources-customizing-pipelinerun-as-code_{context}"]
+.Additional resources
+
+* xref:../pac/install-config-pipelines-as-code.adoc#customizing-pipelines-as-code-configuration_install-config-pipelines-as-code[Customizing {pac} configuration]

pac/install-config-pipelines-as-code.adoc

@@ -22,7 +22,7 @@ include::modules/op-pac-additional-controller.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../pac/install-config-pipelines-as-code.adoc#customizing-pipelines-as-code-configuration_{context}[Customizing {pac} configuration]
+* xref:../pac/install-config-pipelines-as-code.adoc#customizing-pipelines-as-code-configuration_install-config-pipelines-as-code[Customizing {pac} configuration]
 
 * xref:../pac/using-pipelines-as-code-repos.adoc#pac-configuring-github-app-manually_using-pipelines-as-code-repos[Configuring a GitHub App manually and creating a secret for {pac}]