Why We Use Git Branches and Pull Requests
Git is the system we use to track every change to your code. Branches and pull requests are how we keep work organised, reviewed and safe before it joins the main codebase.
Think of a branch as a private workspace and a pull request as a formal proposal to merge that work in.
How the Workflow Flows
- A developer creates a branch for a specific feature or fix.
- They make and test their changes there, in isolation.
- They open a pull request to propose merging the work.
- Colleagues review it and the automated checks run.
- Once approved and passing, it merges into the main code.
Why This Protects Your Project
Branches mean unfinished work never affects the live product. Pull requests create a written record of what changed, why, and who approved it — invaluable for accountability and for understanding the history of your software later.
Because every change is small, isolated and reviewed, several developers can work in parallel without treading on one another. This keeps delivery moving steadily even on a busy project with multiple features in flight at once.
Frequently Asked Questions
Does this slow down getting a change live?
Only marginally, and the trade is well worth it: the review and history you gain prevent far costlier mistakes down the line.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.