Skip to content
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

Unset backport branch's remote from upstream #85

Merged
merged 2 commits into from
Aug 15, 2023

Conversation

ambv
Copy link
Contributor

@ambv ambv commented Aug 2, 2023

This way the user can easily commit and push further changes to the backport, if needed, without having to remember to append their fork's remote name to git push.

The branch sets the upstream as the remote during git checkout -b. This isn't a useful default as we push the resulting backport to the user's fork anyway and it is never intended to either merge further upstream changes nor to push to upstream directly.

ambv added 2 commits July 31, 2023 17:02
This way the user can easily commit and push further changes to the backport,
if needed, without having to remember to append their fork's remote name to
`git push`.

The branch sets the upstream as the remote during `git checkout -b`. This isn't
a useful default as we push the resulting backport to the user's fork anyway
and it is never intended to either merge further upstream changes nor to push
to upstream directly.
@ambv ambv merged commit e4ece75 into main Aug 15, 2023
42 checks passed
@ambv ambv deleted the backport-remote-should-be-own-fork branch August 15, 2023 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant