📚 Sync docs from alaudadevops/tektoncd-operator on 26ad4b3a4fc1166b077d072e8a8775aece73b1a9

Source: docs(crds): update crds information (#439)
Author: edge-katanomi-app2[bot]
Ref: refs/heads/main
Commit: 26ad4b3a4fc1166b077d072e8a8775aece73b1a9

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

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

Author: edge-katanomi-app2[bot]

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-08-11 09:24:02 UTC
+- **Last synced**: 2025-09-03 06:06:46 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3](https://github.com/alaudadevops/tektoncd-operator/commit/9e1a9dc8a45ad0123347d5d61cf8a8b8890a49e3)
-- **Triggered by**: tik-seven
-- **Workflow run**: [#33](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16876030255)
+- **Source commit**: [26ad4b3a4fc1166b077d072e8a8775aece73b1a9](https://github.com/alaudadevops/tektoncd-operator/commit/26ad4b3a4fc1166b077d072e8a8775aece73b1a9)
+- **Triggered by**: edge-katanomi-app2[bot]
+- **Workflow run**: [#43](https://github.com/alaudadevops/tektoncd-operator/actions/runs/17423042800)
 
 ## 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

@@ -448,7 +448,7 @@ CEL expressions typically correspond one-to-one with JSON/protobuf fields. In Te
 
 #### Using Operators
 
-Now that we can access fields, you can create filters using operators. Here’s a list of operators that can be used in CEL expressions:
+Now that we can access fields, you can create filters using operators. Here's a list of operators that can be used in CEL expressions:
 
 | Operator                | Description                | Example                                      |
 | ----------------------- | -------------------------- | -------------------------------------------- |
@@ -463,7 +463,7 @@ Now that we can access fields, you can create filters using operators. Here’s
 
 #### Using Functions
 
-Many functions can be used in CEL expressions. Here’s a list of functions that can be used in CEL expressions. The strings in function parameters represent the expected type of the arguments:
+Many functions can be used in CEL expressions. Here's a list of functions that can be used in CEL expressions. The strings in function parameters represent the expected type of the arguments:
 
 | Function                                             | Description                 | Example                                      |
 | ----------------------------------------------------| ----------------------------| -------------------------------------------- |
@@ -482,7 +482,7 @@ You can also nest function calls and mix operators to create complex filtering e
 
 ### Using CEL Filtering Expressions with gRPC
 
-You can pass a filter to gRPC requests by specifying `filter=<cel-expression>`. Be sure to use the correct quoting in your queries or escape if necessary. Here’s an example:
+You can pass a filter to gRPC requests by specifying `filter=<cel-expression>`. Be sure to use the correct quoting in your queries or escape if necessary. Here's an example:
 
 ```bash
 grpc_cli call --channel_creds_type=ssl \
@@ -494,7 +494,7 @@ grpc_cli call --channel_creds_type=ssl \
 
 ### Using CEL Filtering Expressions with REST
 
-You can pass a filter to REST requests by specifying `filter=<cel-expression>` in your query. Here’s an example:
+You can pass a filter to REST requests by specifying `filter=<cel-expression>` in your query. Here's an example:
 
 ```bash
 curl --insecure \
@@ -505,7 +505,7 @@ curl --insecure \
 
 ### Using CEL Filtering Expressions with `tkn-results`
 
-If you have installed `tkn-results` CLI independently or as a plugin to `tkn`, you can filter Results using the `--filter=<cel-expression>` flag. Here’s an example:
+If you have installed `tkn-results` CLI independently or as a plugin to `tkn`, you can filter Results using the `--filter=<cel-expression>` flag. Here's an example:
 
 ```bash
 tkn results records list default/results/- --filter="data.metadata.annotations.contains('bar')"
@@ -544,6 +544,8 @@ To request a list of objects in a specific order, include the `order_by` query p
 
 Fields supported in `order_by`:
 
+<!-- lint ignore table-size -->
+
 | Field Name       |
 | ---------------- |
 | `create_time`   |

docs/en/apis/advanced_apis/results/intro.md

@@ -178,6 +178,8 @@ There are several ways to specify input and output artifacts:
 - Used to track source code repository details
 - Helps in provenance generation for source code
 
+{/* lint ignore code-block-split-list */}
+
 ```yaml
 results:
   - name: CHAINS-GIT_URL
@@ -186,7 +188,7 @@ results:
     type: string
 ```
 
-:::details{title="Example TaskRun"}
+:::details \{title="Example TaskRun"}
 ```yaml
 apiVersion: tekton.dev/v1
 kind: TaskRun
@@ -228,6 +230,8 @@ spec:
 - Used to specify input artifacts that influenced the build process
 - Helps track dependencies and source materials
 
+{/* lint ignore code-block-split-list */}
+
 ```yaml
 results:
   - name: first-ARTIFACT_INPUTS
@@ -237,7 +241,7 @@ results:
       digest: {}
 ```
 
-:::details{title="Example TaskRun"}
+:::details \{title="Example TaskRun"}
 ```yaml
 apiVersion: tekton.dev/v1
 kind: TaskRun
@@ -280,7 +284,7 @@ results:
     type: string
 ```
 
-:::details{title="Example TaskRun"}
+:::details \{title="Example TaskRun"}
 ```yaml
 apiVersion: tekton.dev/v1
 kind: TaskRun
@@ -310,13 +314,15 @@ spec:
 - Can specify multiple images, separated by commas or newlines
 - Each image must include the complete digest
 
+{/* lint ignore code-block-split-list */}
+
 ```yaml
 results:
   - name: IMAGES
     type: string
 ```
 
-:::details{title="Example TaskRun"}
+:::details \{title="Example TaskRun"}
 ```yaml
 apiVersion: tekton.dev/v1
 kind: TaskRun
@@ -342,6 +348,8 @@ spec:
 - Similar to IMAGE_URL/IMAGE_DIGEST but with different naming convention
 - Used for specifying artifact location and its digest
 
+{/* lint ignore code-block-split-list */}
+
 ```yaml
 results:
   - name: first-ARTIFACT_URI
@@ -355,6 +363,8 @@ results:
 - Uses object type results
 - Must include uri and digest fields
 
+{/* lint ignore code-block-split-list */}
+
 ```yaml
 results:
   - name: first-ARTIFACT_OUTPUTS
@@ -364,7 +374,7 @@ results:
       digest: {}
 ```
 
-:::details{title="Example TaskRun"}
+:::details \{title="Example TaskRun"}
 ```yaml
 apiVersion: tekton.dev/v1
 kind: TaskRun