- We use trunk based development for libraries - create a feature branch from
main, e.g.feature/new-feature - Pull requests must contain a succinct, clear summary of what the user need is driving this feature change
- Ensure your branch contains logical atomic commits before sending a pull request - follow the alphagov Git styleguide
- You may rebase your branch after feedback if it's to include relevant updates from the main branch. We prefer a rebase here to a merge commit as we prefer a clean and straight history on develop with discrete merge commits for features