Summary: GitHub Actions as the CI/CD interface between code and infrastructure across all 7Mind repos. Sources: TBD — fill from workflow files in each repo Last updated: 2026-05-15
Role in the Stack
GitHub Actions is the primary interface between code changes and infrastructure. It handles test runs, builds, deployments, and Terraform applies. Agents should not manually trigger deploys — all deployments happen through workflows.
Workflow Inventory
TBD — list the key workflows across repos, with repo, filename, trigger, and target:
| Repo | Workflow file | Trigger | Target |
|---|---|---|---|
| flutter-app | TBD | TBD | App Store / Google Play |
| elixir-backend | TBD | TBD | GCP (prod) |
| nuxt-website | TBD | TBD | Cloudflare Pages |
| brain (this repo) | TBD | push to main | Quartz + Cloudflare Pages |
Secrets Convention
TBD — where secrets are stored (org-level vs repo-level), naming convention (e.g. GCP_SA_KEY_PROD, CF_API_TOKEN), and who has access to add/rotate them.
Terraform Apply Flow
TBD — which workflow applies Terraform? What triggers a plan vs apply? Is there a manual approval step?
Gotchas
TBD — any non-obvious behaviors agents should know (e.g. “the deploy workflow requires a manual tag, not just a push to main”, “workflow X caches dependencies and needs a cache-bust key change when deps change”).