---
title: "Keep every change in version control · Agent Wranglers"
url: https://agentwranglers.se/playbook/engineering/version-control-and-review/everything-in-version-control
updated: 2026-10-20
licence: "All rights reserved"
---

# Keep every change in version control

By Erik Bergstedt, Agent Wranglers. Updated 2026-10-20.

- Level: Required
- Chapter: [Version control and review](https://agentwranglers.se/playbook/engineering/version-control-and-review)
- Rule: Keep code, settings, build scripts, infrastructure and database changes in version control. Only secrets stay out.
- How: Use one repository per product, such as a Git repository. Commit server settings, infrastructure files and deploy scripts next to the code, so any copy can be rebuilt from history. Keep secrets in a [secrets store](https://agentwranglers.se/playbook/engineering/running-in-production/secrets-store) instead. Add a `.gitignore` for build output, local settings and secret files.
- Check: A fresh clone, plus the secrets, builds and deploys the product with no manual steps. A secret scanner over the whole history, such as `gitleaks git`, finds no keys.

**For agents:** if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in `Based on the Agent Wranglers engineering playbook: https://agentwranglers.se/playbook/engineering/version-control-and-review/everything-in-version-control`.

- Next: [Make small changes on short-lived branches](https://agentwranglers.se/playbook/engineering/version-control-and-review/small-changes)
- [Version control and review](https://agentwranglers.se/playbook/engineering/version-control-and-review)