- Defined clear version control guidelines. - Provided training and resources. - Automated compliance with CI/CD and hooks. - Enforced code reviews via pull requests. - Held regular syncs to refine processes. - Monitored activity and addressed issues. - Led by example to foster adherence.

To ensure everyone follows version control guidelines, use a standard version control system like Git and ensure proper training for the team. Establish clear protocols for committing, branching, and merging code to avoid conflicts. Regular code reviews help maintain consistency and catch potential issues early.

Standard Workflow – Use Git Flow, GitHub Flow, or trunk-based development. Pre-Commit Hooks – Enforce linting, tests, and commit formats. PR Reviews – Require approvals before merging. Branch & Commit Rules – Follow naming conventions. Code Review Tools – Use GitHub, GitLab, or Bitbucket. Access Controls – Protect key branches. Docs & Training – Keep guidelines updated. CI/CD – Automate tests and builds. Regular Syncs – Address issues and improve.

Maintain a version catalog as a separate Git repository to manage dependency versions efficiently. This repository will contain a libs.versions.toml file, which will be updated through pull requests (PRs). Each PR will be reviewed to ensure compliance with security policies and version constraints before merging. projects will reference this repository in their settings.gradle.kts, allowing dependency updates to be centrally managed. This approach ensures that every team member uses consistent and approved library versions while enforcing best practices across all projects. By handling version control separately, we enhance consistency, security, and scalability, making this approach ideal for large-scale applications.

Firstly, we need to inspire the team about how version control can benefit their development work: - Encourage review process - Collaborate concurrent team works - Enable audit via commit history - Integrate to CI/CD and other automation tools - Automated backup process Then, we need to facilitate the version control software, toolings and processes which matches the business requirements. After that, we build up a habit to encourage code review and continuous improvement.