Lines Matching refs:branch

7 ## Select the integration branch
10 …branches created by developers to add or change a feature. A new feature branch is the basis for e…
17 The `release` branch contains the latest PETSc release including bug-fixes.
32 The `main` branch contains everything in the release branch as well as new features that have passe…
45 ## Start a new feature branch
49 - Create and switch to a new feature branch:
56   For example, Barry’s new feature branch on removing CPP in `snes/` will
63   Use all lowercase and no additional underscores in the branch name.
110 - Push the feature branch to the remote repository as desired:
116 ## Test your branch
142 Often a branch's commit history does not present a logical series of changes.
164 If the branch has already been pushed, the rewritten branch is not compatible with the remote copy …
167 $ git push -f origin branch-name
170 …remote branch with your copy. This must be done with extreme care and only if you know someone els…
171 … a `git pull` immediately after you rebase since that will merge the old branch (from GitLab) into…
173 You can use `git log` to see the recent changes to your branch and help determine what commits shou…
179 ## Rebase your branch against the integration branch
181 …branch onto to the latest version of your {any}`integration branch <sec_integration_branches>` [^r…
186 $ git branch myname/component-feature-backup-1  # optional
195 [^rebase-not-merge-upstream]: Rebasing is generally preferable to [merging an upstream branch](http…  argument