In the GitHub flow, what is typically the first step?

In the GitHub flow, what is typically the first step?

• A. Merging
• B. Committing
• C. Branching
• D. Cloning

Answer: (C)

Starting work in GitHub flow by creating a dedicated branch off the main line of development establishes an isolated workspace for your changes. This keeps the main branch stable while you implement a feature or fix, and it sets up the sequence for review and integration. After the branch exists, you make your commits on that branch, push it to the remote, and then open a pull request to merge back into main once the changes are reviewed and tested. Cloning is just the initial setup to get the repo locally, and merging is the later integration step, not the first action.

Starting work in GitHub flow by creating a dedicated branch off the main line of development establishes an isolated workspace for your changes. This keeps the main branch stable while you implement a feature or fix, and it sets up the sequence for review and integration. After the branch exists, you make your commits on that branch, push it to the remote, and then open a pull request to merge back into main once the changes are reviewed and tested. Cloning is just the initial setup to get the repo locally, and merging is the later integration step, not the first action.