Commit 93cd268e authored by Taylor Patterson's avatar Taylor Patterson
Browse files

Update CONTRIBUTING.md

Correcting some grammatical errors.
parent 9eadd253
......@@ -11,19 +11,19 @@ The full set of ICE developer guidelines are availalbe [here](https://wiki.eclip
Apologies in advance for the extra work required here - this is necessary to comply with the Eclipse Foundation's
strict IP policy.
Please also read [this](http://wiki.eclipse.org/Development_Resources/Contributing_via_Git)
Please also read [this](http://wiki.eclipse.org/Development_Resources/Contributing_via_Git).
In order for any contributions to be accepted you MUST do the following things.
In order for any contributions to be accepted, you MUST do the following things:
* Sign the [Eclipse Foundation Contributor License Agreement](http://www.eclipse.org/legal/CLA.php).
To sign the Eclipse CLA you need to:
* Obtain an Eclipse Foundation userid. Anyone who currently uses Eclipse Bugzilla or Gerrit systems already has one of those.
* Obtain an Eclipse Foundation account. Anyone who currently uses Eclipse Bugzilla or Gerrit already has an Eclipse account.
If you don’t, you need to [register](https://dev.eclipse.org/site_login/createaccount.php).
* Login into the [projects portal](https://projects.eclipse.org/), select “My Account”, and then the “Contributor License Agreement” tab.
* Login to the [projects portal](https://projects.eclipse.org/), select “My Account”, and then the “Contributor License Agreement” tab.
* Add your github username in your Eclipse Foundation account settings. Log in it to Eclipse and go to account settings.
* Add your GitHub ID in your Eclipse Foundation account. Find this option in the "Account Settings" tab.
* "Sign-off" your commits
......@@ -35,16 +35,16 @@ You do this by adding the `-s` flag when you make the commit(s), e.g.
## Making your changes
* Fork the repository on GitHub
* Create a new branch for your changes
* Make your changes
* Make sure you include tests
* Make sure the test suite passes after your changes
* Commit your changes into that branch
* Use descriptive and meaningful commit messages
* If you have a lot of commits squash them into a single commit
* Fork the repository on GitHub.
* Create a new branch for your changes.
* Make your changes.
* Make sure you include tests.
* Make sure the test suite passes after your changes.
* Commit your changes into that branch.
* Use descriptive and meaningful commit messages.
* If you have a lot of commits, squash them into a single commit.
* Make sure you use the `-s` flag when committing as explained above.
* Push your changes to your branch in your forked repository
* Push your changes to your branch in your forked repository.
## Submitting the changes
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment