Skip to content

Say where each cpflow cohort loads its actions #859

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
justin808 wants to merge 1 commit into from
Closed

Say where each cpflow cohort loads its actions #859

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions .github/testing-github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading