📚 Sync documentation from source-docs

Source: docs: Update runtime configuration tep to clarify merge behavior
Author: qingliu
Commit: e8300463cad815e08e4c3025ca8d752cebac656d

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

🔗 View source commit: https://github.com/alaudadevops/tektoncd-operator/commit/e8300463cad815e08e4c3025ca8d752cebac656d
🤖 Synced on 2025-07-03 07:54:44 UTC

Author: web-flow

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-02 06:41:21 UTC
+- **Last synced**: 2025-07-03 07:54:44 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [35c2fc38ce5a3fd145e64a1e22acf30ae7ce9d1b](https://github.com/alaudadevops/tektoncd-operator/commit/35c2fc38ce5a3fd145e64a1e22acf30ae7ce9d1b)
-- **Triggered by**: lentil1016
-- **Workflow run**: [#4](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16017978615)
+- **Source commit**: [e8300463cad815e08e4c3025ca8d752cebac656d](https://github.com/alaudadevops/tektoncd-operator/commit/e8300463cad815e08e4c3025ca8d752cebac656d)
+- **Triggered by**: l-qing
+- **Workflow run**: [#7](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16044776144)
 
 ## Files synced:
 - docs/

docs/en/teps/0001_triggertemplate_runtime_config.md

@@ -478,11 +478,11 @@ spec:
 
 - **env merged by `name` field**: Environment variables are merged by name, same names are overridden
 - **volumes merged by `name` field**: Volumes are merged by name, same names are overridden
-- **Other fields use standard merge**: `nodeSelector`, `securityContext` and other fields use standard merge logic (later values override earlier ones)
+- **Other fields use standard merge**: `nodeSelector`, `securityContext` and other fields use standard merge logic. If the field is an object, it will be recursively merged.
 - **Example**:
   - `BUILD_ENV` is overridden from `"development"` to `"production"`
   - `shared-config` volume is overridden from `configMap` to `secret`
-  - `securityContext` is completely merged
+  - `securityContext` fields are recursively merged (same fields overridden, different fields preserved)
 
 This merge mechanism ensures configuration flexibility and composability, allowing users to create complex runtime configurations by combining multiple templates.
 

docs/en/triggers/trouble_shooting/pipeline_not_triggered.mdx

@@ -1,14 +1,13 @@
 ---
 weight: 10
-sourceSHA: 4894d6ee9f6876a61b243b991087cc3b3083a7c424fdf0374d5300a347099774
 ---
 
 
 # The Pipeline is not automatically triggered
 
 ## Problem Description
 
-After creating the `Pipeline` and `Trigger` using `Pipelines` functionality through the UI console, the `Pipeline` is not automatically triggered event though the event is sent (i.e the code is pushed).
+After creating the `Pipeline` and `Trigger` using `Pipelines` functionality through the UI console, the `Pipeline` is not automatically triggered even though the event is sent (i.e the code is pushed).
 
 ## Root Cause Analysis
 
@@ -19,18 +18,18 @@ There are several possible causes for this issue:
 3. The `ServiceAccount` used by the `EventListener` deployment does not have enough permissions.
 4. The `Trigger` is not configured correctly.
 
-## Problem Investigation 
+## Problem Investigation
 
-Given the possible issues mentioned above, follow the steps to find the root cause of the problem: 
+Given the possible issues mentioned above, follow the steps to find the root cause of the problem:
 
-### Webhook configuration was not setup correctly 
+### Webhook configuration was not set up correctly
 
   1. Access your repository/settings using an account with appropriate permissions.
   2. Check all webhook settings and confirm with the platform administrator details regarding the target address of the webhook.
-  3. Make sure the required events are enabled by the webhook. For Gitlab events please refer to [GitLab Event Triggers](../how_to/gitlab_events.mdx)
-  
+  3. Make sure the required events are enabled by the webhook. For Gitlab events, please refer to [GitLab Event Triggers](../how_to/gitlab_events.mdx)
 
-### EventLister not deployed or setup incorrectly
+
+### EventListener not deployed or set up incorrectly
 
   1. Verify with the Platform Administrator that the `EventListener` was deployed and can be reached from the event source (i.e Gitlab instance).
   2. Access the `EventListener` resource and check if it is listening `Triggers` in the target namespace checking the `EventListener` resource `spec`, it should have the `namespaceSelector` field set to `*` or listing the target namespace.