From 38677aa4702e1bf56278967f92d6b8ae300df772 Mon Sep 17 00:00:00 2001 From: Drummond Dawson Date: Thu, 18 Oct 2018 21:03:53 -0400 Subject: [PATCH] Add missing space to heading for it to render properly --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 197e9bef945..90342cdb1a6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,7 +47,7 @@ Create your topic branch to be submitted as a pull request from master. The Spri # Use short branch names Branches used when submitting pull requests should preferably be named according to GitHub issues, e.g. 'gh-1234' or 'gh-1234-fix-npe'. Otherwise, use succinct, lower-case, dash (-) delimited names, such as 'fix-warnings', 'fix-typo', etc. This is important, because branch names show up in the merge commits that result from accepting pull requests, and should be as expressive and concise as possible. -#Keep commits focused +# Keep commits focused Remember each ticket should be focused on a single item of interest since the tickets are used to produce the changelog. Since each commit should be tied to a single GitHub issue, ensure that your commits are focused. For example, do not include an update to a transitive library in your commit unless the GitHub is to update the library. Reviewing your commits is essential before sending a pull request.