Lines Matching full:branch
220 The workflow described below assumes a single change per branch.
221 It is also possible to prepare a sequence of (usually related) changes in a single branch.
280 <h3 id="master">Switch to the master branch</h3>
283 Most Go installations use a release branch, but new changes should
284 only be made based on the master branch.
285 (They may be applied later to a release branch as part of the release process,
287 Before making a change, make sure you start on the master branch:
317 $ git change <i><branch></i>
322 The name <i><branch></i> is an arbitrary one you choose to identify the
323 local branch containing your changes.
327 (In Git terms, <code>git</code> <code>change</code> <code><branch></code>
328 runs <code>git</code> <code>checkout</code> <code>-b</code> <code>branch</code>,
329 then <code>git</code> <code>branch</code> <code>--set-upstream-to</code> <code>origin/master</code>,
344 # On branch foo
382 # On branch foo
392 the command and move that file to a different branch.
428 (In Git terms, <code>git</code> <code>change</code> with no branch name
518 <code>change</code> <code><i><branch></i></code>.
525 To update your local branch, run
558 To check out the original branch and stop rebasing, run "git rebase --abort".
576 You are currently rebasing branch 'mcgillicutty' on 'a24c3eb'.
579 (use "git rebase --abort" to check out the original branch)
653 To revert, change back to the branch you were working in.
660 submit it to the master branch using the Gerrit UI.
