Skip to content

Enhance the push cmd to also track the newly pushed branch #2049

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.

Sign up for GitHub

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

Open
kevzoid wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Enhance the push cmd to also track the newly pushed branch #2049

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Enhance the push cmd to also track the newly pushed branch
  • Loading branch information
@kevzoid
kevzoid committed Sep 13, 2025
commit 9df645524982c12be6e70c5d58f4002f2244b399
4 changes: 2 additions & 2 deletions book/05-distributed-git/sections/contributing.asc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -582,7 +582,7 @@ For example, if you want to submit a second topic of work to the project, don't
$ git checkout -b featureB origin/master
... work ...
$ git commit
$ git push myfork featureB
$ git push -u myfork featureB
$ git request-pull origin/master myfork
... email generated request pull to maintainer ...
$ git fetch origin
Expand Down Expand Up @@ -623,7 +623,7 @@ $ git checkout -b featureBv2 origin/master
$ git merge --squash featureB
... change implementation ...
$ git commit
$ git push myfork featureBv2
$ git push -u myfork featureBv2
----

The `--squash` option takes all the work on the merged branch and squashes it into one changeset producing the repository state as if a real merge happened, without actually making a merge commit.
Expand Down