8000 bug #3455 [Contributing][Code] fix indentation so that the text is re… · symfony/symfony-docs@6831b13 · GitHub
[go: up one dir, main page]

Skip to content

Commit 6831b13

committed
bug #3455 [Contributing][Code] fix indentation so that the text is rendered properly (xabbuh)
This PR was merged into the 2.3 branch. Discussion ---------- [Contributing][Code] fix indentation so that the text is rendered properly | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | Commits ------- fe5abd3 fix indentation so that the text is rendered properly
2 parents 65efcc4 + fe5abd3 commit 6831b13

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

contributing/code/patches.rst

Lines changed: 4 additions & 4 deletions
< 3DAD td data-grid-cell-id="diff-9ce5190740eed1a47e09bb120606d1af0a8cc1e8357fe63c50ab2a6233c39db3-404-404-0" data-selected="false" role="gridcell" style="background-color:var(--bgColor-default);text-align:center" tabindex="-1" valign="top" class="focusable-grid-cell diff-line-number position-relative diff-line-number-neutral left-side">404
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ When your patch is not about a bug fix (when you add a new feature or change
200200
an existing one for instance), it must also include the following:
201201

202202
* An explanation of the changes in the relevant ``CHANGELOG`` file(s) (the
203-
``[BC BREAK]`` or the ``[DEPRECATION]`` prefix must be used when relevant);
203+
``[BC BREAK]`` or the ``[DEPRECATION]`` prefix must be used when relevant);
204204

205205
* An explanation on how to upgrade an existing application in the relevant
206206
``UPGRADE`` file(s) if the changes break backward compatibility or if you
@@ -396,9 +396,9 @@ type this command, an editor will popup showing a list of commits:
396396
397397
To squash all commits into the first one, remove the word ``pick`` before the
398398
second and the last commits, and replace it by the word ``squash`` or just
399-
``s``. When you save, Git will start rebasing, and if successful, will ask
400-
you to edit the commit message, which by default is a listing of the commit
401-
messages of all the commits. When you are finished, execute the push command.
399+
``s``. When you save, Git will start rebasing, and if successful, will ask
400+
you to edit the commit message, which by default is a listing of the commit
401+
messages of all the commits. When you are finished, execute the push command.
402402

403403
.. _ProGit: http://git-scm.com/book
404
.. _GitHub: https://github.com/signup/free

0 commit comments

Comments
 (0)
0