1 files changed, 1 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b819e0b9..054b9a3f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -57,6 +57,7 @@ Please report any problem you might find.
 * starting from branch ` master`, switch to a new branch (eg. `git checkout -b my-awesome-feature`)
 * edit the required files (from the Github web interface or your text editor)
 * add and commit your changes with a meaningful commit message (eg `Cool new feature, fixes issue #1001`)
+ * run unit tests against your patched version, see [Running unit tests](https://github.com/shaarli/Shaarli/wiki/Running-unit-tests)
 * Open your fork in the Github web interface and click the "Compare and Pull Request" button, enter required info and submit your Pull Request.
 All changes you will do on the `my-awesome-feature`  in the future will be added to your Pull Request. Don't work directly on the master branch, don't do unrelated work on your  `my-awesome-feature` branch.

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b819e0b9..054b9a3f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md
@@ -57,6 +57,7 @@ Please report any problem you might find.
57	* starting from branch ` master`, switch to a new branch (eg. `git checkout -b my-awesome-feature`)	57	* starting from branch ` master`, switch to a new branch (eg. `git checkout -b my-awesome-feature`)
58	* edit the required files (from the Github web interface or your text editor)	58	* edit the required files (from the Github web interface or your text editor)
59	* add and commit your changes with a meaningful commit message (eg `Cool new feature, fixes issue #1001`)	59	* add and commit your changes with a meaningful commit message (eg `Cool new feature, fixes issue #1001`)
		60	* run unit tests against your patched version, see [Running unit tests](https://github.com/shaarli/Shaarli/wiki/Running-unit-tests)
60	* Open your fork in the Github web interface and click the "Compare and Pull Request" button, enter required info and submit your Pull Request.	61	* Open your fork in the Github web interface and click the "Compare and Pull Request" button, enter required info and submit your Pull Request.
61		62
62	All changes you will do on the `my-awesome-feature` in the future will be added to your Pull Request. Don't work directly on the master branch, don't do unrelated work on your `my-awesome-feature` branch.	63	All changes you will do on the `my-awesome-feature` in the future will be added to your Pull Request. Don't work directly on the master branch, don't do unrelated work on your `my-awesome-feature` branch.