Skip to content

Commit cff20f9

Browse files
committedJan 28, 2025
Update branch in CONTRIBUTING instructions
1 parent 115bac0 commit cff20f9

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed
 

‎CONTRIBUTING.rst

+6-6
Original file line numberDiff line numberDiff line change
@@ -29,9 +29,9 @@ Initial Set-up
2929
git remote add upstream https://github.com/xdebug/xdebug.git
3030
git fetch upstream
3131

32-
- Add a tracking branch for Xdebug 3.3::
32+
- Add a tracking branch for Xdebug 3.4::
3333

34-
git checkout --track origin/xdebug_3_3
34+
git checkout --track origin/xdebug_3_4
3535

3636
Branches
3737
--------
@@ -40,18 +40,18 @@ There are two branches in operation:
4040

4141
``master``
4242
This is were all new feature Pull Requests should be targeted at
43-
``xdebug_3_3``
43+
``xdebug_3_4``
4444
This is were all bug fix Pull Requests should be targeted at. The
4545
maintainer will add them to ``master`` too when merging the Pull Request.
4646

4747
Working on a Pull Request
4848
-------------------------
4949

50-
- Make sure that your ``master`` and ``xdebug_3_3`` branches are up to date
50+
- Make sure that your ``master`` and ``xdebug_3_4`` branches are up to date
5151
with the ``upstream`` repository.
5252
- Create an issue in the `issue tracker <https://bugs.xdebug.org>`_ (if none
5353
exists yet).
54-
- Switch to the right target branch (``master`` for features, ``xdebug_3_3``
54+
- Switch to the right target branch (``master`` for features, ``xdebug_3_4``
5555
for bug fixes).
5656
- Create a feature branch::
5757

@@ -89,7 +89,7 @@ Working on a Pull Request
8989
will be targeting, for example to rebase against the current bug fix
9090
branch::
9191
92-
git fetch upstream && git rebase upstream/xdebug_3_3
92+
git fetch upstream && git rebase upstream/xdebug_3_4
9393
9494
- Push your changes to your remote repository::
9595

0 commit comments

Comments
 (0)
Please sign in to comment.