Question

A developer on your team is about to start work on an experimental new checkout feature. They are worried that their unfinished code could break the stable version of the application that other teammates are currently relying on. Which Git concept should they use to keep this new work isolated from the main line of development until it is ready?

Accepted Answer

Create a new branch for the checkout feature and commit their changes there

Answer

Make all commits directly to the main branch so the history stays in one place

Answer

Clone the repository a second time and work in the duplicate copy

Answer

Open an issue describing the feature and attach the code as a Markdown snippet