@@ -51,15 +51,15 @@ With the hook initialized in a repository, create branches being sure to include
51
51
the Pivotal Tracker story number in the branch name.
52
52
53
53
``` bash
54
- $ git checkout -b a_useful_and_helpful_name_8675309
54
+ $ git switch -c best_feature_ever_8675309
55
55
```
56
56
57
57
When you commit, Git will fire the hook which will find the story number in the
58
58
branch name and prepare your commit message so that it includes the story number
59
59
in the [ special Pivotal Tracker syntax] [ pt-format ] .
60
60
61
61
``` bash
62
- # on branch named `best_feature_ever-8675309 `
62
+ # on branch named `best_feature_ever_8675309 `
63
63
$ git commit
64
64
```
65
65
@@ -72,7 +72,7 @@ the top)*
72
72
[#8675309]
73
73
# Please enter the commit message for your changes. Lines starting
74
74
# with '#' will be ignored, and an empty message aborts the commit.
75
- # On branch best_feature_ever-8675309
75
+ # On branch best_feature_ever_8675309
76
76
# Changes to be committed:
77
77
# (use "git reset HEAD <file>..." to unstage)
78
78
#
@@ -89,7 +89,7 @@ If you pass a commit message on the command line the hook will still add the
89
89
story number, preceded by an empty line, to the end of your message.
90
90
91
91
``` bash
92
- # on branch named `best_feature_ever-8675309 `
92
+ # on branch named `best_feature_ever_8675309 `
93
93
$ git commit -m' Look at this rad code, yo!'
94
94
```
95
95
@@ -105,7 +105,7 @@ However, if you include the story number in the Pivotal Tracker format within
105
105
your commit message, the hook will do nothing.
106
106
107
107
``` bash
108
- # on branch named `best_feature_ever-8675309 `
108
+ # on branch named `best_feature_ever_8675309 `
109
109
$ git commit -m' [#8675309] Look at this rad code, yo!'
110
110
```
111
111
@@ -156,12 +156,11 @@ name, optionally prefixing it with a hash (`#`). Examples:
156
156
# # Contributing :octocat:
157
157
158
158
1. Fork it
159
- 2. Create your feature branch (` git checkout -b my_new_feature` )
159
+ 2. Create your feature branch (` git switch -c my_new_feature` )
160
160
3. Commit your changes (` git commit -am ' Added some feature' ` )
161
161
4. Push to the branch (` git push origin my_new_feature` )
162
162
5. Create new Pull Request
163
163
164
-
165
164
[pt]: https://www.pivotaltracker.com/
166
165
[pt-format]: https://www.pivotaltracker.com/help/api? version= v3#scm_post_commit_message_syntax
167
166
[tpope]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
0 commit comments