Use code fence syntax around git workflow for readability.

This commit is contained in:
Jen Hamon
2015-04-01 13:25:32 -07:00
parent 5cae401c98
commit 76bc0a87db

View File

@@ -12,18 +12,17 @@ We welcome your contributions! Thanks for helping make Jasmine a better project
Please submit pull requests via feature branches using the semi-standard workflow of: Please submit pull requests via feature branches using the semi-standard workflow of:
1. Fork it ```bash
1. Clone your fork: (`git clone git@github.com:yourUserName/jasmine.git`) git clone git@github.com:yourUserName/jasmine.git # Clone your fork
1. Change directory: (`cd jasmine`) cd jasmine # Change directory
1. Assign original repository to a remote named 'upstream': (`git remote add git remote add upstream https://github.com/jasmine/jasmine.git # Assign original repository to a remote named 'upstream'
upstream https://github.com/jasmine/jasmine.git`) git fetch upstream # Pull in changes not present in your local repository
1. Pull in changes not present in your local repository: (`git fetch upstream`) git checkout -b my-new-feature # Create your feature branch
1. Create your feature branch (`git checkout -b my-new-feature`) git commit -am 'Add some feature' # Commit your changes
1. Commit your changes (`git commit -am 'Add some feature'`) git push origin my-new-feature # Push to the branch
1. Push to the branch (`git push origin my-new-feature`) ```
1. Create new Pull Request
We favor pull requests with very small, single commits with a single purpose. Once you've pushed a feature branch to your forked repo, you're ready to open a pull request. We favor pull requests with very small, single commits with a single purpose.
## Background ## Background