From bb3e56d2b3e15decdc851e3bb817d404da0379e0 Mon Sep 17 00:00:00 2001
From: Joel Takvorian <jtakvori@redhat.com>
Date: Wed, 16 Oct 2019 17:07:42 +0200
Subject: [PATCH] Doc: work is based on master; push to fork

Doc was mentioning branch "develop" (which doesn't exist it seems) instead of master
Refer to forked repo instead of upstream
---
 support/guides/contributing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/support/guides/contributing.md b/support/guides/contributing.md
index 84d58c7ba..264cb4820 100644
--- a/support/guides/contributing.md
+++ b/support/guides/contributing.md
@@ -178,10 +178,10 @@ Mobilizon can be developed locally. For instructions on how to do this, please s
 
 #### How to make changes
 
-* Make your changes on a separate branch which includes an issue number e.g. `1234-some-new-feature` where 1234 is the issue number where the feature is documented. Make sure the branch is based on `develop`.
+* Make your changes on a separate branch which includes an issue number e.g. `1234-some-new-feature` where 1234 is the issue number where the feature is documented. Make sure the branch is based on `master`.
 * Do not commit changes to files that are irrelevant to your feature or bugfix.
 * Use commit messages descriptive of your changes.
-* Push to the upstream of your new branch.
+* Push to your own repository fork.
 * Create a merge request at GitLab.
 
 #### Git commit messages