Open a pull request that is easy to review

A pushed branch becomes collaborative when you propose how it should enter another branch and give reviewers the context needed to evaluate it.

A pull request compares a head/compare branch containing proposed changes with a base branch that would receive them. The PR updates as new commits are pushed to the compare branch.

A strong description explains the problem, approach, important trade-offs, testing performed and any screenshots or migration notes needed. Keep the scope focused enough to review.

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

git switch -c feature/search
# edit, test, commit
git push -u origin feature/search

# Optional with GitHub CLI:
gh pr create --base main --head feature/search --fill

Pushing the branch and opening the pull request are separate operations. The PR does not replace the Git commits; it organizes review around them.

Your task: Write a PR description for a two-file change using four headings: Why, What changed, How tested, Reviewer notes.

Do not bundle unrelated refactors, formatting and features into one huge PR when they can be separated. Review quality falls when the reviewer cannot isolate intent.

Open a pull request that is easy to review 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.