Merge pull request #701 from ldennington/update-contributing-guidelines

Update contributing guidelines

Author: ldennington

CONTRIBUTING.md

@@ -1,13 +1,14 @@
 # Contributing
 
-[issue]: https://github.com/GitCredentialManager/git-credential-manager/issues
+[issue]: https://github.com/GitCredentialManager/git-credential-manager/issues/new/choose
 [fork]: https://github.com/GitCredentialManager/git-credential-manager/fork
 [pr]: https://github.com/GitCredentialManager/git-credential-manager/compare
 [code-of-conduct]: CODE_OF_CONDUCT.md
+[commits]: https://www.youtube.com/watch?v=4qLtKx9S9a8
 
-Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+Hi there! We're thrilled that you'd like to contribute to GCM :tada:. Your help is essential for keeping it great.
 
-Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+Contributions to GCM are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
 
 Please note that this project is released with a [Contributor Code of Conduct][code-of-conduct]. By participating in this project you agree to abide by its terms.
 
@@ -29,6 +30,7 @@ This helps us coordinate and reduce duplication.
     - `GitHub.UI.Avalonia`
     - `Atlassian.Bitbucket.UI.Windows`
     - `GitHub.UI.Windows`
+1. Organize your changes into one or more [logical, descriptive commits][commits].
 1. Push to your fork and [submit a pull request][pr]
 1. Pat your self on the back and wait for your pull request to be reviewed and merged.
 
@@ -37,7 +39,6 @@ Here are a few things you can do that will increase the likelihood of your pull
 - Match existing code style.
 - Write tests.
 - Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
-- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 
 ## Resources