From 810f4ed0f13252fe4e730455a80e214ddfd89f74 Mon Sep 17 00:00:00 2001 From: Alejandra Ferreiro Vidal Date: Wed, 6 Dec 2017 17:29:16 +0100 Subject: [PATCH] add info about working with forks --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bc95aca1e..d97b2b7ca 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,6 +14,10 @@ Use the issue tracker to find ways to contribute. Find a bug or a feature, menti Generally speaking, you should fork this repository, make changes in your own fork, and then submit a pull-request. All new code should have been thoroughly tested end-to-end in order to validate implemented features and the presence or lack of defects. +### Working with forks +[Configure this repository as a remote for your own fork](https://help.github.com/articles/configuring-a-remote-for-a-fork/) +[And sync your fork with this repository](https://help.github.com/articles/syncing-a-fork/) before beginning to work on a new pull-request. + ### Tests All pipeline library coding _must_ come with automated unit tests.