CI/CD Template Consolidation — Action Required

[danielvm-git]

CI/CD Template Consolidation — Action Required

The .github template repo has been redesigned. 16 separate workflow templates → 9 unified pipelines.

What changed

Every ci-cd-*.yml template now follows a 3-stage pipeline:

ci → verify → deploy

• ci: Language-specific lint, typecheck, test, build
• verify: Preflight + conventional commits + no AI attribution
• deploy: Conditional BigBase deploy (skip if no secrets)

New templates available

Template	For	Deploy Target
ci-cd-node.yml	Node.js	BigBase
ci-cd-python.yml	Python (uv/pip/matrix)	BigBase
ci-cd-go.yml	Go	BigBase
ci-cd-static.yml	Static sites (Astro, Vue, React)	BigBase
ci-cd-swift.yml	Swift (macOS)	—
ci-cd-monorepo.yml	Multi-language	BigBase
ci-cd-pages-mkdocs.yml	MkDocs docs	GitHub Pages
ci-cd-pages-starlight.yml	Starlight docs	GitHub Pages
codeql.yml	Security scanning	—

How to migrate

1. Copy template: cp ~/Developer/.github/workflow-templates/ci-cd-<language>.yml .github/workflows/ci-cd.yml
2. Configure: Set APP_TYPE and SITE_URL env vars
3. Remove old workflows: ci.yml, release.yml, deploy.yml etc.
4. Validate: yamllint .github/workflows/ci-cd.yml
5. Push and verify CI passes

Resources

• Migration plan: docs/how-to/migrate-ci-cd/migration-plan.md in danielvm-git/.github
• Template picker: Copy from workflow-templates/ in danielvm-git/.github
• Naming convention: Function (Scope) — e.g. CI, CI/CD, Deploy (BigBase), CodeQL

Timeline

Please migrate within 2 weeks. The old templates will be removed after all repos are migrated.

Questions? Comment on this issue.

[danielvm-git]

Naming Convention (Updated)

The naming convention uses Function (Scope) pattern:

Type	Pattern	Examples
CI	CI	CI — build/test only
CI/CD	CI/CD	CI/CD — build/test + deploy
Deploy	Deploy (Target)	Deploy (BigBase), Deploy (GitHub Pages)
Docs	Deploy Docs	Deploy Docs — documentation deployment
CodeQL	CodeQL or CodeQL (Language)	CodeQL, CodeQL (JavaScript), CodeQL (Python)
Release	Release or Release (Target)	Release, Release (BigBase)

[danielvm-git]

What changed

Every ci-cd-*.yml template now follows a 4-stage pipeline:

ci → verify → semantic-release → deploy

• ci: Language-specific lint, typecheck, test, build
• verify: Preflight + conventional commits + no AI attribution
• semantic-release: Version bump, changelog, GitHub release (main branch only)
• deploy: Conditional BigBase deploy (skip if no secrets)

[danielvm-git]

How to Work with the Templates Repository

The .github template repo (danielvm-git/.github) is now the single source of truth for CI/CD across all repos.

Quick Start

# 1. Clone the templates repo (one-time)
git clone https://github.com/danielvm-git/.github.git ~/Developer/.github

# 2. Copy the template for your stack
cp ~/Developer/.github/workflow-templates/ci-cd-<language>.yml .github/workflows/ci-cd.yml

# 3. Configure
# Edit .github/workflows/ci-cd.yml:
# - Set APP_TYPE (static, python, node, go)
# - Set SITE_URL (https://<slug>.bigbase.click)

# 4. Remove old workflows
rm .github/workflows/ci.yml .github/workflows/release.yml  # etc.

# 5. Validate and push
yamllint .github/workflows/ci-cd.yml
git add -A && git commit -m "refactor: consolidate CI/CD into single pipeline"
git push

Available Templates

Template	Stack	Pipeline
ci-cd-node.yml	Node.js	ci → verify → semantic-release → deploy
ci-cd-python.yml	Python	ci → verify → semantic-release → deploy
ci-cd-go.yml	Go	ci → verify → semantic-release → deploy
ci-cd-static.yml	Static sites	ci → verify → semantic-release → deploy
ci-cd-swift.yml	Swift	ci → verify (no deploy yet)
ci-cd-monorepo.yml	Multi-language	ci → verify → semantic-release → deploy
ci-cd-pages-mkdocs.yml	MkDocs docs	ci → verify → deploy (GitHub Pages)
ci-cd-pages-starlight.yml	Starlight docs	ci → verify → deploy (GitHub Pages)
codeql.yml	Security	weekly scan

Pipeline Stages

ci → verify → semantic-release → deploy

• ci: Lint, typecheck, test, build
• verify: Preflight + conventional commits + no AI attribution
• semantic-release: Version bump, changelog, GitHub release (main only)
• deploy: Conditional BigBase deploy (skips if no secrets)

Naming Convention

All workflow name: fields follow Function (Scope):

• CI or CI/CD
• Deploy (BigBase), Deploy (GitHub Pages)
• CodeQL, CodeQL (JavaScript), CodeQL (Python)
• Release, Release (BigBase)

Resources

• Templates: workflow-templates/ in danielvm-git/.github
• Migration plan: docs/how-to/migrate-ci-cd/migration-plan.md
• Deploy action: danielvm-git/.github/actions/bigbase-deploy@main
• Naming convention: docs/how-to/migrate-ci-cd/migration-plan.md § Naming Convention

Need Help?

Comment on this issue or check the migration guide above.