Summary: Where CI and deployments run for the repos that make up 7Mind today. GitHub Actions is common to all of them, but the deploy step differs: Codemagic for the app, Cloudflare Pages for the website, manual Lambda dispatch, Argo CD or Jenkins on the Gymondo platform. Sources: workflow files in sevenmind/7mind-mobile-apps-monorepo, sevenmind/website-next-js, sevenmind/backend, sevenmind/api-contracts, Gymondo-git/function-sevenmind-legacy-gateway, Gymondo-git/frontend-public-pages (Jenkinsfile), Gymondo-git/actions, Gymondo-git/kubernetes-apps; sevenmind/backend origin/main workflows and terraform/environment/staging/RETIRED.md re-read on 2026-11-09 Last updated: 2026-11-09
Workflow inventory
| Repo | CI | Deploy |
|---|---|---|
| 7mind-mobile-apps-monorepo | GitHub Actions (test.yml, analyze.yml, and others) | Codemagic builds and ships iOS and Android. See mobile-build-pipeline |
| website-next-js | GitHub Actions ci.yml (Vitest, ESLint only) | Cloudflare Pages builds main and every PR |
| function-sevenmind-legacy-gateway | GitHub Actions test.yaml on PRs | Manual Build workflow dispatch, using Gymondo-git/actions function.yaml to push to ECR and run aws lambda update-function-code |
Other Gymondo function-* repos | GitHub Actions | Same shared function.yaml workflow |
| Gymondo EKS services | GitHub Actions or Jenkins | Argo CD syncs Gymondo-git/kubernetes-apps; image bumps arrive as automated “update config” PRs |
| frontend-public-pages | Jenkins | Jenkins servicePipeline to Gymondo Kubernetes |
| elixir-backend (legacy) | GitHub Actions (mix check) | deploy-to-production.yml on GitHub Release: builds the image and applies the repo’s production Terraform to GKE. deploy-catalogue-builder.yml publishes the content builder image to AWS via GitHub OIDC (main to test, a release to production). The staging deploy was deleted on 2026-10-07 together with the staging plane |
| api-contracts | GitHub Actions check.yml | GitHub Pages via publish-main.yml |
| brain (this repo) | none | Cloudflare Pages builds Quartz on push to main |
Terraform apply flow
Only one Terraform location applies from CI: the terraform/ folder of sevenmind/backend, whose production root is applied by deploy-to-production.yml on every published release. sevenmind/infrastructure is applied by hand with just apply <target> after a reviewed PR; Gymondo-git/terraform by hand per workspace with make. See terraform.
Gotchas
- Deploying a Gymondo Lambda ships only the binary. Kong routes, CloudFront behaviours and env vars are Terraform and need their own apply.
- The 7Mind engineers lost admin rights on the
sevenmindGitHub org around 2026-07-29 (date not verified). The org sits inside the 7NXT GitHub Enterprise; platform-unification dates the join to 2026-01-30, also not verified, so the join and the loss of admin rights may be two separate events. Org-level secrets and settings now go through the platform team. - The website’s CI deliberately skips the build; a broken build shows up as a failed Cloudflare Pages preview, not as a failed GitHub check.