DevOps Overview
Delivery and branching
RHEA uses AEM Edge Delivery Services, so there is no traditional deploy step — EDS serves files directly from the GitHub repository. Every push to a branch produces an instantly accessible preview at https://{branch}--rhea--aa-pdcoe.aem.page/.
- develop — default integration branch; feature PRs target it.
- main — production branch; develop is promoted to main for release.
- Feature branches: feat/eds-{issue#}, fix/eds-{issue#}, etc. Branch names stay under 63 chars (EDS preview URLs are DNS subdomains).
Which branch serves which environment is in the Architecture Overview.
Quality gates
Locally, via a Husky pre-commit hook, which builds and stages generated artifacts so compiled output is always committed:
- Merges component-model JSON when _*.json / *.config.json change.
- Compiles SCSS + regenerates design tokens when .scss / figma-tokens.json change.
- Runs lint:fix across the codebase.
In CI, via GitHub Actions:
- build.yml — on push (any branch) runs lint; on PRs into develop/main also runs a Snyk security scan.
- playwright.yml — runs the Playwright E2E suite on PRs/pushes to develop/stage/main, against the branch's own preview. See Quality Assurance.
- Dependency updates via Renovate (.renovaterc.json).
Build system (committed artifacts)
Because EDS serves from the repo, all compiled artifacts (.min.css, merged component JSON, generated token SCSS) must be committed. That is what the pre-commit hook above exists to guarantee. The build handles SCSS→CSS (sass + PostCSS autoprefixer), design-token generation (Style Dictionary), and JSON component-model merging.
Where to go for detail
| Topic | Source |
|---|---|
| Workflow definitions | .github/workflows/ |
| Pre-commit hook | .husky/ |
| Build scripts + npm scripts | build-scripts/, package.json |
| Repoless site config & CI (Cloudflare, Admin API) | abbvie-migrated/eds-site-config |