📚 Sync docs from alaudadevops/tektoncd-operator on 9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3

Source: update triggertemplate_concept docs (#304)
Author: tik-seven
Ref: refs/heads/main
Commit: 9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: AlaudaDevops/tektoncd-operator@9e1a9dc
🤖 Synced on 2025-08-11 09:24:02 UTC

Author: tik-seven

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-08-11 08:21:47 UTC
+- **Last synced**: 2025-08-11 09:24:02 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [b2a7119ab75231d5dd9f04ff3ef836825a5e6c27](https://github.com/alaudadevops/tektoncd-operator/commit/b2a7119ab75231d5dd9f04ff3ef836825a5e6c27)
+- **Source commit**: [9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3](https://github.com/alaudadevops/tektoncd-operator/commit/9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3)
 - **Triggered by**: tik-seven
-- **Workflow run**: [#32](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16874693446)
+- **Workflow run**: [#33](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16876030255)
 
 ## Files synced:
 - docs/

docs/en/triggers/concepts/triggertemplate_concept.mdx

@@ -70,6 +70,8 @@ TriggerTemplates are essential in the following scenarios:
 
 5. **Parameterized Testing**: Create test pipelines with different parameters based on the type of event.
 
+6. **As Runtime Configuration Templates**: Provide standardized runtime configurations (such as parameters, workspaces, security contexts, etc.) for repeatedly executed Pipelines. Users can select matching templates through the frontend UI to quickly generate pipelinerun instances that meet scenario requirements.
+
 ## Constraints and Limitations
 
 - Parameters in TriggerTemplates can only be string values
@@ -140,6 +142,28 @@ Each created resource receives labels to track its origin:
 - `tekton.dev/eventlistener: <EventListenerName>`
 - `tekton.dev/triggers-eventid: <EventID>`
 
+### Runtime Configuration Templates
+
+1. Label Conventions
+
+- `triggertemplate.triggers.tekton.dev/usage: runtime-config`
+
+  Must be set to `runtime-config` to identify the purpose of the template.
+
+- `tekton.dev/pipeline: <pipeline-name>`
+
+  Associates the template with a specific pipeline.
+
+- `triggertemplate.triggers.tekton.dev/runtime-config-default: "true"`
+
+  Optional, marks the template as the default configuration for the pipeline. If multiple default templates exist, the one with the latest creation timestamp will be selected.
+
+2. Resource Template Conventions
+
+- Only one `PipelineRun` resource can be defined in `spec.resourcetemplates`.
+- Must include `pipelineRef` to reference the target pipeline.
+- Supports all runtime configuration fields of `PipelineRun`, such as `params`, `workspaces`, `podTemplate`, etc.
+
 ## Configuration Examples
 
 ### Basic CI Pipeline Template
@@ -242,6 +266,39 @@ spec:
             value: $(tt.params.git-revision)
 ```
 
+### Runtime Configuration Template
+
+```yaml
+apiVersion: triggers.tekton.dev/v1beta1
+kind: TriggerTemplate
+metadata:
+  name: deploy-pipeline-staging-config
+  labels:
+    triggertemplate.triggers.tekton.dev/usage: runtime-config
+    tekton.dev/pipeline: deploy-pipeline
+    triggertemplate.triggers.tekton.dev/runtime-config-default: true
+spec:
+  resourcetemplates:
+    - apiVersion: tekton.dev/v1
+      kind: PipelineRun
+      metadata:
+        generateName: deploy-pipeline-staging-
+      spec:
+        pipelineRef:
+          name: deploy-pipeline
+        params:
+          - name: environment
+            value: "staging"
+          - name: replicas
+            value: "2"
+        workspaces:
+          - name: config
+            configMap:
+              name: staging-config
+```
+
+
+
 ## Important Parameter Explanations Related to TriggerTemplate
 
 ### Parameter Substitution