Skip to content

[Contributing] Replace "ticket" with "issue" #19062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 20, 2023
Merged

[Contributing] Replace "ticket" with "issue" #19062

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions contributing/code/pull_requests.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,8 +172,8 @@ Then create a new branch off the ``5.4`` branch to work on the bug fix:

.. tip::

Use a descriptive name for your branch (``ticket_XXX`` where ``XXX`` is the
ticket number is a good convention for bug fixes).
Use a descriptive name for your branch (``fix_XXX`` where ``XXX`` is the
issue number is a good convention for bug fixes).

The above checkout commands automatically switch the code to the newly created
branch (check the branch you are working on with ``git branch``).
Expand Down Expand Up @@ -338,7 +338,7 @@ Symfony as quickly as possible.
Some answers to the questions trigger some more requirements:

* If you answer yes to "Bug fix?", check if the bug is already listed in the
Symfony issues and reference it/them in "Fixed tickets";
Symfony issues and reference it/them in "Issues";

* If you answer yes to "New feature?", you must submit a pull request to the
documentation and reference it under the "Doc PR" section;
Expand Down