Skip to content

Rollout — TECH_STACK §7 staging dispatch docs #25

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

Merged
blackbrowed-labs merged 2 commits into from
May 13, 2026
Merged

Rollout — TECH_STACK §7 staging dispatch docs #25

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
30830ae
chore(docs): document staging dispatch workflow in TECH_STACK §7
blackbrowed-labs May 13, 2026
6424dd9
Merge pull request #24 from blackbrowed-labs/chore/tech-stack-staging…
blackbrowed-labs May 13, 2026
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
4 changes: 2 additions & 2 deletions docs/TECH_STACK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -388,8 +388,8 @@ Release notes are language-neutral (GitHub releases have one version each). They

1. In every product repo under `blackbrowed-labs`, a GitHub Actions workflow triggers on `release: published`.
2. That workflow sends a `repository_dispatch` event to the website repo with `event_type: product-release-published` and a payload containing the product slug and release tag.
3. In the website repo, a workflow listens for that event type and triggers a production deploy.
4. During the build, the `releases` content loader re-fetches from the GitHub API. New release appears.
3. In the website repo, two workflows listen for that event type and trigger production and staging deploys in parallel (`.github/workflows/rebuild-on-dispatch.yml` and `.github/workflows/rebuild-on-dispatch-staging.yml`). The pair mirrors the per-environment-file convention already in use for `deploy-{staging,production}.yml` and `rebuild-nightly{,-staging}.yml`.
4. During each build, the `releases` content loader re-fetches from the GitHub API. New release appears on both environments within ~60 seconds.

Cross-repo PAT with `actions: write` on the website repo lives as a secret in each product repo.

Expand Down
Loading