From e7f9e673ac8166037d3b054e066fe5f72441fc7c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Boulogne?= Date: Wed, 10 Jul 2013 18:51:18 +0200 Subject: [PATCH] minor modifications --- CONTRIBUTING.txt | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/CONTRIBUTING.txt b/CONTRIBUTING.txt index 20e6cff0..331b4ed8 100644 --- a/CONTRIBUTING.txt +++ b/CONTRIBUTING.txt @@ -154,25 +154,24 @@ detailing the test coverage:: skimage/filter/__init__ 1 1 100% ... -Activate Travis-ci for your fork (optional) ----------------------------------------- +Activate Travis-CI for your fork (optional) +------------------------------------------- -Travis-ci checks all unittests in the project to prevent breakage. +Travis-CI checks all unittests in the project to prevent breakage. -Before sending a pull request, you may want to check that Travis-ci +Before sending a pull request, you may want to check that Travis-CI successfully passes all tests. To do so, - * Go to `Travis-ci `__ and follow the Sign In link at the top:: + * Go to `Travis-CI `__ and follow the Sign In link at the top - * Go to your `profile page `__ - - * Switch on your scikit-image fork + * Go to your `profile page `__ and switch on your + scikit-image fork It corresponds to steps one and two in -`Travis-ci documentation `__ +`Travis-CI documentation `__ (Step three is already done in scikit-image). -Thus, as soon as you push your code to your fork, it will trigger Travis-ci, +Thus, as soon as you push your code to your fork, it will trigger Travis-CI, and you will receive an email notification when the process is done. Bugs