|
2 | 2 |
|
3 | 3 | These commands are generated by [cpflow](https://github.com/shakacode/control-plane-flow). |
4 | 4 | For full setup, version-pinning, and troubleshooting details, see the upstream |
5 | | -[CI automation guide](https://github.com/shakacode/control-plane-flow/blob/c0ca750c4838dacf6a1d81d52cb151301516cb77/docs/ci-automation.md). |
| 5 | +[CI automation guide](https://github.com/shakacode/control-plane-flow/blob/54a6b8a066ac0a59c49e95a866e21b5633e2b1f9/docs/ci-automation.md). |
6 | 6 |
|
7 | 7 | ## Pull Request Commands |
8 | 8 |
|
@@ -56,7 +56,7 @@ the environment approval gate passes. |
56 | 56 | ## Version Locking |
57 | 57 |
|
58 | 58 | Generated wrappers pin Control Plane Flow once with the reusable workflow |
59 | | -`uses:` ref, for example `@c0ca750c4838dacf6a1d81d52cb151301516cb77`. For stable releases, |
| 59 | +`uses:` ref, for example `@54a6b8a066ac0a59c49e95a866e21b5633e2b1f9`. For stable releases, |
60 | 60 | this ref should be a release tag. The upstream reusable workflow automatically |
61 | 61 | loads its matching shared actions from GitHub's workflow context, so downstream |
62 | 62 | wrappers should not pass a duplicate Control Plane Flow ref input. If your |
@@ -91,5 +91,8 @@ Most apps do not need these: |
91 | 91 | | `CPLN_CLI_VERSION` | Pin a specific `@controlplane/cli` version; normally leave unset. | |
92 | 92 |
|
93 | 93 | The PR-open help workflow posts a short command reference whenever the generated |
94 | | -wrapper exists. Remove `.github/workflows/cpflow-review-app-help.yml` or add a |
95 | | -wrapper-level `if:` guard if a repo should not advertise review apps. |
| 94 | +wrapper exists. That is intentional for configured demo repos. Forks or clones |
| 95 | +that copy the workflow before configuring Control Plane can remove |
| 96 | +`.github/workflows/cpflow-review-app-help.yml` or uncomment and adapt the |
| 97 | +wrapper-level `if:` guard shown in that file, for example |
| 98 | +`vars.REVIEW_APP_PREFIX != '' || vars.CPLN_ORG_STAGING != ''`. |
0 commit comments