From 2f42d998057f2e7fb763851b45561dc92090f18d Mon Sep 17 00:00:00 2001 From: "flamingo[bot]" <277372822+flamingo[bot]@users.noreply.github.com> Date: Fri, 25 Sep 2026 18:26:25 +0000 Subject: [PATCH] =?UTF-8?q?chore:=20add=20=F0=9F=A6=A9=20Flamingo=20Code?= =?UTF-8?q?=20Documentation=20workflow?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This workflow enables automated documentation generation using the 🦩 Flamingo Code Documentation pipeline. It runs on repository_dispatch events triggered by the multi-platform-hub. No secrets required - all credentials are passed securely at runtime. --- .github/workflows/code-documentation.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/code-documentation.yml b/.github/workflows/code-documentation.yml index 6fe16448..de9324b5 100644 --- a/.github/workflows/code-documentation.yml +++ b/.github/workflows/code-documentation.yml @@ -20,8 +20,8 @@ # Stages 2 (Claude), 3 and 4 follow the code reviewer's agentic pattern # (templates/scripts/code-documentation-lib.mjs): the hub serves this # repository's settings, the script packs the material, ONE hub call writes -# ONE document (forced `emit_document`; the hub's read tools when the -# repository's "Graph lookups" switch is on), a deterministic gate checks every +# ONE document (forced `emit_document`; the hub's read tools once the +# repository's visibility is resolved), a deterministic gate checks every # repository path it names, and the script, never the model, picks where each # document is written. # @@ -2513,9 +2513,9 @@ jobs: # STAGE 3: TUTORIALS # Getting-started guides and how-to tutorials, written by the Code # Documentation lane (code-documentation-lib.mjs): one hub call per - # tutorial with the forced `emit_document` tool and, when the repository's - # "Graph lookups" switch is on, the hub's read tools (the code graph and - # the rules, scoped to what THIS repository may see). No model key here. + # tutorial with the forced `emit_document` tool and, once the repository's + # visibility is resolved, the hub's read tools (the code graph and the + # rules, scoped to what THIS repository may see). No model key here. # Generates 4 tutorials: user/getting-started, user/common-use-cases, # dev/getting-started-dev, dev/architecture-overview-dev # =========================================================================