File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -172,8 +172,8 @@ Then create a new branch off the ``5.4`` branch to work on the bug fix:
172
172
173
173
.. tip ::
174
174
175
- Use a descriptive name for your branch (``ticket_XXX `` where ``XXX `` is the
176
- ticket number is a good convention for bug fixes).
175
+ Use a descriptive name for your branch (``fix_XXX `` where ``XXX `` is the
176
+ issue number is a good convention for bug fixes).
177
177
178
178
The above checkout commands automatically switch the code to the newly created
179
179
branch (check the branch you are working on with ``git branch ``).
@@ -338,7 +338,7 @@ Symfony as quickly as possible.
338
338
Some answers to the questions trigger some more requirements:
339
339
340
340
* If you answer yes to "Bug fix?", check if the bug is already listed in the
341
- Symfony issues and reference it/them in "Fixed tickets ";
341
+ Symfony issues and reference it/them in "Issues ";
342
342
343
343
* If you answer yes to "New feature?", you must submit a pull request to the
344
344
documentation and reference it under the "Doc PR" section;
You can’t perform that action at this time.
0 commit comments