The problem
An agency team works across dozens of client codebases at once, with support fixes and project work happening side by side. Without shared rules, every repository drifts its own way: branches nobody can trace, releases that are hard to audit, and quality that depends on who happened to review the change.
What I put in place
- One Git workflow for every project. Branches named after their ticket, commit messages that carry the ticket key, production and staging changed only through pull requests, and every release tied to a release ticket rather than a date.
- Support never waits for projects. Support fixes branch from production, while project work lives on epic branches, so unfinished features never block an urgent fix.
- Quality checks that run themselves. GrumPHP pre-commit hooks run the Magento and PSR coding standards on every commit, so standards are enforced before code reaches a reviewer.
- Consistent environments. Documented remote development environments and DevOps references for each project, so a developer can pick up any codebase quickly.
- AI assistants that follow the rules. A shared, version-controlled configuration gives every developer’s coding assistant the same coding standards and project context, with secrets kept out of Git.
Why it matters
Code quality shouldn’t depend on memory or goodwill. When the right way is also the easy, automated way, the whole team does it, and every client benefits from code the next developer can understand.