Lines Matching refs:pull

53 local branch. Local branches can be configured to automerge (on pull)
62 And pull new changes from the repository, and update your local
65   % git pull
67 Assuming we are on the branch C<blead> immediately after a pull, this
146   % git pull
267 L<https://help.github.com/en/articles/creating-a-pull-request-from-a-fork>.
556 =head2 Working with Github pull requests
562 However Github does provide a mechanism to fetch a pull request to a
563 local branch.  They are available on Github remotes under C<pull/>, so
564 you can use C<< git fetch pull/I<PRID>/head:I<localname> >> to make a
565 local copy.  eg.  to fetch pull request 9999 to the local branch
568   git fetch origin pull/9999/head:local-branch-name
581 Alternatively you can configure the remote to fetch all pull requests
590 Add a line to map the remote pull request branches to remote-tracking
596           fetch = +refs/pull/*/head:refs/remotes/origin/pull/*
602 This will create a remote-tracking branch for every pull request, including
735  rejected Merge the remote changes (e.g. 'git pull') before pushing
795   % git pull --rebase
820 remote branch C<origin/maint-5.005>. Then you can pull, commit, merge
867   % git pull