Branches and pull requests

A branch is a separate copy of the code where you can make changes without affecting what is live. The main branch should always match what is deployed in production.

A simple workflow

1. Create a branch named after the change, for example feature/ice-orders-epr-refresh.
2. Make and test the change in your TIE test environment, then export and commit it to the branch.
3. Open a pull request describing what changed, why, the clinical safety impact and how it was tested.
4. A colleague reviews it. Automated checks run.
5. Once approved, merge into main and deploy to live using your change process.

Why this matters

• Nothing reaches main without a second pair of eyes.
• Each pull request is a ready-made change record for your CAB.
• If something breaks, you can see exactly which change caused it and revert it.

Environment branches (optional)

Some teams keep test and main branches matching their test and live TIE environments, promoting changes from one to the other.