From 890a7be0c63af9ca8bc36b521fda0a8e043906f6 Mon Sep 17 00:00:00 2001 From: Andrew Dolgov Date: Wed, 5 Jul 2017 18:51:24 +0300 Subject: [PATCH] update contributing.md --- CONTRIBUTING.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ec792d7bd..025af843d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,9 +2,11 @@ *or: how I learned to post merge requests without crying myself to sleep* -1. Post your idea on the forums. Preferably post diffs if you got them. Mention your gitlab username. If everything looks fine, you'll be granted developer permissions for the project in question. -2. When you have developer privileges you can make branches, check them out, work on them locally, push them back and post merge requests. -3. Usual stuff applies: don't post unrelated issues in one merge request, try to not screw up indenting (tt-rss mostly uses tab characters), try to respect surrounding formatting style, etc. +1. Post your idea on the forums. Preferably post diffs if you got them. Mention your Gogs username. +If everything looks fine, you'll be granted developer permissions for the project in question. +2. When you have developer privileges you can make branches, check them out, work on them locally, +push them back and post merge requests. +3. Usual stuff applies: don't post unrelated issues in one merge request, try to not screw up +indenting (tt-rss mostly uses tab characters), try to respect surrounding formatting style, etc. 4. That's it. -Note: while Gitlab allows requesting access permissions for the project bots or random people kept silently spamming this feature so I had to disable it. -fox \ No newline at end of file