Skip to content

Commit b35e62b

Browse files
committed
[Contributing] Clarify the rebase operation
I just mentioned the fact that `push -f` is usually required when rebasing and explicit that the "2.2 when bugfixing" is a follow up on the previous example (Not necessarily explicit at first).
1 parent 780cd22 commit b35e62b

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

contributing/code/patches.rst

+3-2
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,8 @@ while to finish your changes):
228228
229229
.. tip::
230230

231-
Replace `master` with `2.2` if you are working on a bugfix
231+
Replace ``master`` with the branch you selected previously (e.g. ``2.2``)
232+
if you are working on a bugfix
232233

233234
When doing the ``rebase`` command, you might have to fix merge conflicts.
234235
``git status`` will show you the *unmerged* files. Resolve all the conflicts,
@@ -243,7 +244,7 @@ Check that all tests still pass and push your branch remotely:
243244

244245
.. code-block:: bash
245246
246-
$ git push origin BRANCH_NAME
247+
$ git push -f origin BRANCH_NAME
247248
248249
Make a Pull Request
249250
~~~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)