-
-
Notifications
You must be signed in to change notification settings - Fork 851
Prefer upstream for main #943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Would this mean pushing to Usually there's no need to push to But some people may have muscle memory, because it's a very common thing to do with forks (see all these upvotes, and "Syncing a fork" is quite high in GitHub's "Collaborating with pull requests" docs). Another rare but occasional use case for pushing to main: wanting to test your own changes on CI when the CI is locked to only run for |
The devguide should be updated to show how to configure upstream push as an invalid operation. For example, by supplying an invalid URL for such an operation. |
Yes, it seems that's the case :(
It looks like maybe the upstream 'push' can be configured to also point to the user's fork:
That configuration should also address @erlend-aasland's suggestion. Instead of making the push invalid, it just directs it to the user's repo. That also means that a I'll update the docs to reflect this approach. |
This is done in 3fdba64. |
FYI, Since I last visited this issue, I've implemented jaraco.develop.git.configure_fork, which I use to checkout cpython (and other projects to which I contribute through forks) so that I don't have to remember these steps or refer to any documentation and I get consistent behavior across hundreds of projects. |
FYI, merging/rebasing on |
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
…am and push goes to origin.
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
… .git from https.
d7e9065
to
3dee9ad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @jaraco
A reminder that the merge commit message is pre-filled with all commit messages and should be edited to be brief and useful. |
No description provided.