From be273956bfbedad1212e19a415f395bd57ad832f Mon Sep 17 00:00:00 2001 From: Waldemar Znoinski Date: Mon, 24 Oct 2016 12:41:03 +0000 Subject: [PATCH] cleanup references to stackforge Change-Id: I6a74890fec2fc4dec104bbc18a4af2186c8cf7d4 --- CONTRIBUTING.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index a15f8fa..8f22097 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -60,7 +60,7 @@ Ready to contribute? Here's how to set up `intel-nfv-ci-tests` for local develop 1. Fork the `intel-nfv-ci-tests` repo on GitHub. 2. Clone your fork locally:: - $ git clone https://github.com/stackforge/intel-nfv-ci-tests + $ git clone https://github.com/openstack/intel-nfv-ci-tests 3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:: @@ -100,7 +100,7 @@ Before you submit a pull request, check that it meets these guidelines: your new functionality into a function with a docstring, and add the feature to the list in README.rst. 3. The pull request should work for Python 2.6, 2.7, 3.3, and 3.4, and for PyPy. Check - https://travis-ci.org/stackforge/intel-nfv-ci-tests/pull_requests + https://travis-ci.org/openstack/intel-nfv-ci-tests/pull_requests and make sure that the tests pass for all supported Python versions. Tips