For issue #2, Sam branches from main, adds an ?author= clause to app.js, a test and a README line (14 tests pass), pushes the branch and opens the pull request, with its description in a file:
git switch -c feature/author-filter
git commit -qam "Filter books by author with ?author="
git push -u origin feature/author-filter
gh pr create --base main --title "Filter books by author" --body-file pr-author.md \
--label "area: api" --milestone 1.2.0 --assignee @meOutput
remote: Create a pull request for 'feature/author-filter' on GitHub by visiting: remote: https://github.com/binarybehemoth/booknest/pull/new/feature/author-filter ... https://github.com/binarybehemoth/booknest/pull/7
GitHub 29 answers a new branch with a link to its compare page (the remote: lines). Number 7 follows the six issues, which share the sequence. The base (main) receives the change and the head carries it. --fill takes title and body from the commits; --web finishes in the browser. Keep a pull request small and about one thing: reviewers read 200 lines carefully and skim 2,000.