Mariatta added the comment:
No need to feel embarrassed about it :) I've made similar mistake in the past.
Sounds good to rename the "Syncing with Upstream" section with "Updating your
CPython fork".
If you can open an issue in github.com/python/devguide, that would be great. We
can
New submission from E. Paine :
Simple enough: we should make it very clear in the Devguide that creating a PR
from python:master to :master is not a good way to update your fork.
For context, I recently saw that a commit on a fork was showing as a mention on
a lot of the more recent commits
