First Pull Request Etiquette

Etiquette for a First Open-Source Pull Request

Spoon-Knife's image has an empty alt attribute, so screen readers skip it: a typical first contribution, small and easy to review. A real contribution would go upstream with gh 29 pr create -R octocat/Spoon-Knife --head binarybehemoth:describe-octocat-image. This book never opens pull requests on other people's repositories, so Sam opens it inside his fork, naming the fork explicitly:

A fix on a branch of the fork, and a pull request that stays inside the forkShell
git switch -c describe-octocat-image
sed -i 's/id="octocat" alt=""/id="octocat" alt="The Octocat"/' index.html
git commit -qam "Describe the Octocat image for screen readers"
git push -qu origin describe-octocat-image
gh pr create -R binarybehemoth/booknest-fork-spoon-knife --base main --head describe-octocat-image \
  --title "Describe the Octocat image for screen readers" --body-file pr-alt.md
gh pr list -R octocat/Spoon-Knife --author @me --state all --json number
Output
Switched to a new branch 'describe-octocat-image'
https://github.com/binarybehemoth/booknest-fork-spoon-knife/pull/1
[]

The empty list confirms that nothing reached the upstream. Maintainers are volunteers, so make a first pull request easy to accept: