From ea00525bad580ca8ca5a633c4a48fb3d5d8ca1fa Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Tue, 23 Jun 2026 16:44:13 -0700 Subject: [PATCH] Workflows cheat-sheet: clarify shared-- is a naming convention Adds a one-line note to composition gotcha #7 explaining that the `shared--` prefix on `workflow-id` is an optional shared-workflow naming convention, not required syntax. Follow-up to a post-merge review comment on #6826 where the double dash read as a possible typo. The double dash is intentional and documented (shared---), so the YAML example is unchanged; only the clarifying note is added. Co-authored-by: Cursor --- explore-analyze/workflows/reference/cheat-sheet.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/explore-analyze/workflows/reference/cheat-sheet.md b/explore-analyze/workflows/reference/cheat-sheet.md index 1ebe960c31..47e9a978d0 100644 --- a/explore-analyze/workflows/reference/cheat-sheet.md +++ b/explore-analyze/workflows/reference/cheat-sheet.md @@ -262,6 +262,8 @@ Full reference: [Pass data and handle errors](/explore-analyze/workflows/authori alerts: "${{ event.alerts }}" ``` + The `shared--` prefix in the workflow ID is an optional [naming convention](/explore-analyze/workflows/authoring-techniques/compose-workflows.md) for shared workflows, not required syntax. + 8. **`data.*` steps (except `data.set`) put source data at the top level:** `items:`, `arrays:`, or `source:`. The transformation configuration goes in `with`. ```yaml