ci: forward the R2 write pair to staging builds — runs become reviewable in morelli
Staging deploy builds now upload their renders to runs/pcbjam/<run-id>/ like ci-ubicloud does (secrets: inherit there), so render changes on the staging branch can be reviewed and promoted in morelli without a manual ci-ubicloud dispatch. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
91291fde37
commit
471e078a9d
1 changed files with 5 additions and 0 deletions
5
.github/workflows/deploy-staging.yml
vendored
5
.github/workflows/deploy-staging.yml
vendored
|
|
@ -33,6 +33,11 @@ jobs:
|
|||
# too (baselines live in R2 now; without these the fetch/compare steps skip).
|
||||
CI_SCREENSHOTS_S3_ACCESS_KEY_ID: ${{ secrets.CI_SCREENSHOTS_S3_ACCESS_KEY_ID }}
|
||||
CI_SCREENSHOTS_S3_SECRET_ACCESS_KEY: ${{ secrets.CI_SCREENSHOTS_S3_SECRET_ACCESS_KEY }}
|
||||
# Write pair so staging builds also upload their renders to
|
||||
# runs/pcbjam/<run-id>/ — making them reviewable/promotable in morelli
|
||||
# (https://pcbjam-morelli-staging.pcbjam-staging.workers.dev).
|
||||
CI_SCREENSHOTS_S3_WRITE_ACCESS_KEY_ID: ${{ secrets.CI_SCREENSHOTS_S3_WRITE_ACCESS_KEY_ID }}
|
||||
CI_SCREENSHOTS_S3_WRITE_SECRET_ACCESS_KEY: ${{ secrets.CI_SCREENSHOTS_S3_WRITE_SECRET_ACCESS_KEY }}
|
||||
|
||||
publish-and-deploy:
|
||||
needs: build
|
||||
|
|
|
|||
Loading…
Reference in a new issue