From 8135c9ba00e5e1e60fd4f9e6955f9b53a2da5f44 Mon Sep 17 00:00:00 2001 From: Eric Marsman Date: Tue, 26 Apr 2016 13:20:22 -0400 Subject: [PATCH] try new format --- CONTRIBUTING.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 25e0d6b7..31f94ad9 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -13,8 +13,8 @@ Reporting an Issue * Make sure you have a `GitHub account `_ * Check if a ticket already exists for your issue on GitHub_. * If one does not already exist, `create a new ticket`__ - + Clearly describe the issue including steps to reproduce when it is a bug. - + Make sure you include in the earliest version that you know has the issue. + + Clearly describe the issue including steps to reproduce when it is a bug. + + Make sure you include in the earliest version that you know has the issue. __ GitHub_ @@ -25,11 +25,11 @@ Making Changes fix or new feature. * Fork the repository on GitHub * Create a topic branch from where you want to base your work. - + This is usually the master branch. - + Only target release branches if you are certain your fix must be on that branch. - + To quickly create a topic branch based on master: - ``git checkout -b fix/master/my_contribution master`` - + Please avoid working directly on the ``master`` branch. + + This is usually the master branch. + + Only target release branches if you are certain your fix must be on that branch. + + To quickly create a topic branch based on master: + ``git checkout -b fix/master/my_contribution master`` + + Please avoid working directly on the ``master`` branch. * Make commits of logical units. * Check for unnecessary whitespace with `git diff --check` before committing. * Make sure your commit messages are in the `proper