Use GitHub Flow for everyday feature work

GitHub's beginner workflow is intentionally lightweight: make a branch, commit changes, open a pull request and merge after review.

A typical GitHub Flow starts from an updated default branch, creates a descriptive topic branch, makes commits, pushes early, opens a pull request, responds to review and merges when the required checks are satisfied.

The exact team rules can vary. Some teams require approvals, status checks, signed commits, deployments or a merge queue. The principle is that proposed work is visible and reviewable before it changes the protected integration branch.

Run this in a disposable practice repository unless the lesson explicitly says otherwise.

git switch main
git pull --ff-only
git switch -c feature/search
# edit, commit
git push -u origin feature/search
# open PR, review, merge
# delete branch when no longer needed

This workflow keeps feature development isolated while still encouraging early sharing through the remote branch and pull request.

Your task: Write the exact sequence four teammates should follow when each works on a different task. Include what they do before branching and what happens after a PR is merged.

A workflow is useful only when the team follows shared rules. Decide who can merge, which checks are required, whether branches must be current and what to do with urgent fixes.

Use GitHub Flow for everyday feature work is complete when you can explain the state being changed before you run the command, not merely repeat the syntax.

Read further: official supporting documentation.