If you do git hub fork, it would be nice if additionally remote.pushDefault would be set to origin, because that supports the common use-case. I make a new branch for the changes of a PR with git checkout -b my-nifty-change upstream/master, then I prepare the branch, push it to origin and create a PR, then some further changes need to be made and again pushed to origin. Usually you don't have push access to upstream anyway and even if you would have, you shouldn't do it in a PR-based model, but push to the PR branch in your fork.
If you do
git hub fork, it would be nice if additionallyremote.pushDefaultwould be set toorigin, because that supports the common use-case. I make a new branch for the changes of a PR withgit checkout -b my-nifty-change upstream/master, then I prepare the branch, push it tooriginand create a PR, then some further changes need to be made and again pushed toorigin. Usually you don't have push access to upstream anyway and even if you would have, you shouldn't do it in a PR-based model, but push to the PR branch in your fork.