Question

A small development team wants to adopt a lightweight, branch-based workflow. They release updates to their web application several times per day and need every change to be reviewed and validated before it reaches production. Which characteristic of the GitHub Flow makes it well suited to this team's needs?

Accepted Answer

It centers on short-lived feature branches and pull requests, keeping the main branch always deployable after review.

Answer

It requires all changes to be committed directly to the main branch so that deployments happen instantly without review.

Answer

It mandates long-running release branches that are merged only once per quarter to reduce deployment frequency.

Answer

It prevents any collaboration by locking the repository until a single maintainer approves the entire release.