Skip to content

Commit ea05a8e

Browse files
committed
Add marketing site deployment quality gate rules
1 parent 953c777 commit ea05a8e

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

.roo/rules/rules.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,3 +22,15 @@
2222
- Use Tailwind CSS classes instead of inline style objects for new markup
2323
- VSCode CSS variables must be added to webview-ui/src/index.css before using them in Tailwind classes
2424
- Example: `<div className="text-md text-vscode-descriptionForeground mb-2" />` instead of style objects
25+
26+
4. Marketing Site (web-roo-code) Deployment Quality Gates:
27+
28+
- The marketing site deployment workflows (`.github/workflows/website-deploy.yml`, `.github/workflows/website-preview.yml`) must include quality checks before deploying to Vercel
29+
- When modifying these workflows, ensure the following checks run before deployment:
30+
- Linting: `pnpm --filter @roo-code/web-roo-code lint`
31+
- Type checking: `pnpm --filter @roo-code/web-roo-code check-types`
32+
- Build validation: `pnpm --filter @roo-code/web-roo-code build`
33+
- Deployment workflows should either:
34+
- Add a `needs:` dependency on the `code-qa` workflow (for PR-based deployments), OR
35+
- Include a dedicated `quality-checks` job that runs before the `deploy`/`preview` jobs
36+
- Never deploy broken code to production - quality gates prevent deployment of code that fails linting, type-checking, or build steps

0 commit comments

Comments
 (0)