Lines Matching full:branch

57    expose an unstable branch for others to test with or for automated
58    testing services.  If you do expose a branch that may be unstable in
61  - Do not rebase a branch that contains history created by others.  If you
100 which may contain multiple topic branches; each branch is usually developed
102 required before any given branch finds its way into an upstream repository.
132 history into your tree, you cannot rebase that branch, even if you
139 trees tend to be a red flag when it comes time to push a branch upstream.
143 It is natural to want to merge the master branch into a repository; this
150 branch.  They will significantly increase your chances of encountering bugs
155 a well-managed branch.
175 subsystem branch and the mainline?  The most important step is to warn
177 that demonstrates an awareness of how your branch fits into the whole.  For
178 especially difficult conflicts, create and push a *separate* branch to show
179 how you would resolve things.  Mention that branch in your pull request,
180 but the pull request itself should be for the unmerged branch.
200 creating a topic branch dedicated to the prerequisite commits that can be
212 point rather than some random spot.  If your upstream-bound branch has