From 66057034ad4de15c37b11e35f9137e9a66af2e95 Mon Sep 17 00:00:00 2001 From: Justin Gordon Date: Fri, 9 Oct 2026 21:19:13 -1000 Subject: [PATCH] Say where each cpflow cohort loads its actions The GitHub Actions testing note still described only upstream-loaded actions. The 6.0.0 review-app workflows run the checked-in local ones. Co-Authored-By: Claude Opus 5.5 --- .github/testing-github-actions.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/testing-github-actions.md b/.github/testing-github-actions.md index f61cc4c6..a4a2796e 100644 --- a/.github/testing-github-actions.md +++ b/.github/testing-github-actions.md @@ -25,9 +25,11 @@ guide: 4. For comment-triggered review-app commands, test a real `+review-app-deploy` after the trusted default-branch wrapper points at the code under test. 5. Pin upstream `control-plane-flow` workflow and action references to reviewed, - immutable full commit SHAs with readable release comments. Newer upstream - workflows load their matching shared actions automatically; do not add a - duplicate ref input to downstream wrappers. + immutable full commit SHAs with readable release comments. The v5.2.0 + workflows load their matching shared actions from that upstream source; the + 6.0.0 review-app workflows run the actions checked in under + `.github/actions/cpflow-*`. Do not add a duplicate ref input to downstream + wrappers. The review-app deploy/delete pair uses released **6.0.0** together; the other generated callers and promotion actions retain their reviewed **5.2.0** cohort.