From 20ef922dde5b16d9b5e71a4e525ec54bfccfa03d Mon Sep 17 00:00:00 2001 From: Adam Novak Date: Tue, 10 Nov 2015 14:03:43 -0800 Subject: [PATCH] Mention that the correct way to run tests is nosetests --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f48bc2b51..4b0a4b4a2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -26,6 +26,7 @@ Some general rules to follow: * Create a branch for each update that you're working on. These branches are often called "feature" or "topic" branches. Any changes that you push to your feature branch will automatically be shown in the pull request. +* Test your code (by running `nosetests`) before creating a pull request. * Keep your pull requests as small as possible. Large pull requests are hard to review. Try to break up your changes into self-contained and incremental pull requests.