Git Version Control

We use Git version control on every project, with feature branches, pull requests and reviews, so every code change is traceable and reversible.

Where we use it

We use Git for all our projects to manage source code, track changes, and collaborate effectively. Our workflow includes feature branching, pull requests, and code reviews to ensure code quality and a clean project history.

Strengths

Distributed model for offline work and flexibility.
Powerful branching and merging capabilities.
Industry standard for version control.

Trade-offs

Can have a steep learning curve for beginners.
Complex commands for advanced operations.
Large binary files can be problematic to manage.

Questions

A pull request is a way to propose changes to a codebase. It allows other team members to review the changes, discuss them, and suggest modifications before merging them into the main branch.

More in Development Practices & Collaboration

Code Reviews

Every change we ship is reviewed by a second developer for correctness, security and maintainability before it is merged into the main codebase.

CI/CD Pipelines

CI/CD pipelines that automatically build, test and deploy your application, so releases are frequent, repeatable and far less prone to human error.

Git

Git is the distributed version control system used to track source code changes, coordinate developers and keep a full history of every project.