📚 Sync docs from alaudadevops/tektoncd-operator on 6a618335893c5b61c114c57709d03ead259a21e9

Source: docs(crds): update crds information (#436)
Author: l-qing
Ref: refs/heads/release-4.2
Commit: 6a618335893c5b61c114c57709d03ead259a21e9

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

🔗 View source commit: https://github.com/alaudadevops/tektoncd-operator/commit/6a618335893c5b61c114c57709d03ead259a21e9
🤖 Synced on 2025-09-03 06:09:06 UTC

Author: edge-katanomi-app2[bot]

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-08-15 08:54:59 UTC
+- **Last synced**: 2025-09-03 06:09:06 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [33f60382c4cc43a17e38f5bc3592a13e3da88347](https://github.com/alaudadevops/tektoncd-operator/commit/33f60382c4cc43a17e38f5bc3592a13e3da88347)
-- **Triggered by**: l-qing
-- **Workflow run**: [#41](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16986648714)
+- **Source commit**: [6a618335893c5b61c114c57709d03ead259a21e9](https://github.com/alaudadevops/tektoncd-operator/commit/6a618335893c5b61c114c57709d03ead259a21e9)
+- **Triggered by**: edge-katanomi-app2[bot]
+- **Workflow run**: [#42](https://github.com/alaudadevops/tektoncd-operator/actions/runs/17422107876)
 
 ## Files synced:
 - docs/

.yarn/releases/yarn-4.9.2.cjs .yarn/releases/yarn-4.9.4.cjs.yarn/releases/yarn-4.9.2.cjs renamed to .yarn/releases/yarn-4.9.4.cjs

@@ -1,13 +1,14 @@
 ---
 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 even 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 event though the event is sent (i.e the code is pushed).
 
 ## Root Cause Analysis
 
@@ -18,18 +19,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 set up correctly
+### Webhook configuration was not setup 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)
+  
 
-
-### EventListener not deployed or set up incorrectly
+### EventLister not deployed or setup 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.