Version Control and the Path to Production
Changes move from development through staging to production. Automated checks gate staging, and a human from the software department gates production.
DevelopmentGate 1 · automated checksStagingGate 2 · human approvalProduction
Path to production · 2 gates
A failed check or a rejected review sends the work back to its branch. Only reviewed code reaches an official domain.
Requirements
- Version control from day one. All code, configuration and infrastructure definitions live in version control, in a repository owned by the HCI organization rather than a personal account. Nothing is deployed from a local machine or from uploaded files, and every production deployment traces back to a commit.
- Pull requests only. Changes merge through pull requests. The production branch is protected against direct pushes, force-pushes and deletion.
- Automated checks on every pull request. These cover security, dependency and secret scanning, tests, code-quality analysis and an automated AI code review. Merging is blocked until the checks pass and each finding is fixed or explicitly accepted by a reviewer.
- Human approval for production. Merges to production need at least one approval from the software department's review team.
- Official domains. Official HCI domains serve only the reviewed production branch.
- Least-privilege hosting. The software department sets up hosting environments. Development teams get only the permissions they need, such as deploying their own project, and never organization-wide administration.
Recommendations
- Prefer infrastructure as code. Define servers, services, networking and deployment steps in files kept in the repository, and let the pipeline apply them. Keep manual configuration in hosting panels and manual deployments to a minimum, so an environment can be rebuilt, reviewed and audited from the repository alone.
- Keep branches short-lived and pull requests small.
- Merge to staging early so automated feedback arrives long before launch day. Never request the first production review on the day of a deadline.
- Test branches on random, non-official preview domains. (These are provided automatically by HCI’s Coolify instance.)
- Create new repositories from the organization's template, so protections and scanning apply by default.