@@ -24,8 +24,9 @@ Set up your user information with your real name and a working email address:
24
24
$ git config --global user.email you@example.com
25
25
26
26
.. tip ::
27
- If you are new to Git, we highly recommend you to read the excellent and free
28
- `ProGit `_ book.
27
+
28
+ If you are new to Git, we highly recommend you to read the excellent and
29
+ free `ProGit `_ book.
29
30
30
31
Get the Symfony2 code source:
31
32
@@ -61,8 +62,9 @@ topic branch:
61
62
$ git checkout -b BRANCH_NAME
62
63
63
64
.. tip ::
64
- Use a descriptive name for your branch (`ticket_XXX ` where `XXX ` is the ticket
65
- number is a good convention for bug fixes).
65
+
66
+ Use a descriptive name for your branch (`ticket_XXX ` where `XXX ` is the
67
+ ticket number is a good convention for bug fixes).
66
68
67
69
The above command automatically switches the code to the newly created branch
68
70
(check the branch you are working on with `git branch `.)
@@ -82,11 +84,13 @@ in mind the following:
82
84
* Write good commit messages.
83
85
84
86
.. tip ::
85
- A good commit message is composed of a summary (the first line), optionally
86
- followed by a blank line and a more detailed description. The summary should
87
- start with the Component you are working on in square brackets
88
- (`[DependencyInjection] `, `[FrameworkBundle] `, ...). Use a verb (`fixed ... `,
89
- `added ... `, ...) to start the summary and don't add a period at the end.
87
+
88
+ A good commit message is composed of a summary (the first line), optionally
89
+ followed by a blank line and a more detailed description. The summary
90
+ should start with the Component you are working on in square brackets
91
+ (`[DependencyInjection] `, `[FrameworkBundle] `, ...). Use a verb
92
+ (`fixed ... `, `added ... `, ...) to start the summary and don't add a period
93
+ at the end.
90
94
91
95
Submitting a Patch
92
96
------------------
0 commit comments