diff options
| author | Katrina Owen <katrina.owen@gmail.com> | 2012-04-29 15:01:03 +0200 |
|---|---|---|
| committer | Katrina Owen <katrina.owen@gmail.com> | 2012-04-29 15:01:03 +0200 |
| commit | 244e270d16bf3309b57e0cf70397c1d8a6d6f2dc (patch) | |
| tree | 53fbf817be47a74ad7ed70a90773a6f9657e9946 | |
| parent | 8ef7b59427321cec7409408d02b7ea4fd0beb9a4 (diff) | |
| download | bundler-244e270d16bf3309b57e0cf70397c1d8a6d6f2dc.tar.gz | |
Tweak sample commit message.
This admittedly microscopic change encourages best practices as discussed by
@tpope here:
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
| -rw-r--r-- | lib/bundler/templates/newgem/README.md.tt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/bundler/templates/newgem/README.md.tt b/lib/bundler/templates/newgem/README.md.tt index 23a4b10b..98692c55 100644 --- a/lib/bundler/templates/newgem/README.md.tt +++ b/lib/bundler/templates/newgem/README.md.tt @@ -24,6 +24,6 @@ TODO: Write usage instructions here 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) -3. Commit your changes (`git commit -am 'Added some feature'`) +3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request |