Update all documentation footers from generic "April 2026 / 2.1+" to the specific sync date (April 9, 2026) and documented version (2.3.0). Also add version/date footers to zh/CATALOG.md and zh/01-slash-commands/README.md which were missing them. Generated with [Claude Code](https://claude.ai/code) via [Happy](https://happy.engineering) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Happy <yesreply@happy.engineering>
29 lines
1.0 KiB
Markdown
29 lines
1.0 KiB
Markdown
---
|
|
name: Setup CI/CD Pipeline
|
|
description: Implement pre-commit hooks and GitHub Actions for quality assurance
|
|
tags: ci-cd, devops, automation
|
|
---
|
|
|
|
# Setup CI/CD Pipeline
|
|
|
|
Implement comprehensive DevOps quality gates adapted to project type:
|
|
|
|
1. **Analyze project**: Detect language(s), framework, build system, and existing tooling
|
|
2. **Configure pre-commit hooks** with language-specific tools:
|
|
- Formatting: Prettier/Black/gofmt/rustfmt/etc.
|
|
- Linting: ESLint/Ruff/golangci-lint/Clippy/etc.
|
|
- Security: Bandit/gosec/cargo-audit/npm audit/etc.
|
|
- Type checking: TypeScript/mypy/flow (if applicable)
|
|
- Tests: Run relevant test suites
|
|
3. **Create GitHub Actions workflows** (.github/workflows/):
|
|
- Mirror pre-commit checks on push/PR
|
|
- Multi-version/platform matrix (if applicable)
|
|
- Build and test verification
|
|
- Deployment steps (if needed)
|
|
4. **Verify pipeline**: Test locally, create test PR, confirm all checks pass
|
|
|
|
Use free/open-source tools. Respect existing configs. Keep execution fast.
|
|
|
|
---
|
|
**Last Updated**: April 9, 2026
|