From a4682a7a6979a94cf46c303a0fdc148a6362520c Mon Sep 17 00:00:00 2001 From: Andrew Dolgov Date: Tue, 4 Jul 2017 16:46:13 +0300 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 05ae8401..c74844d9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,8 +2,9 @@ *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. -2. If your idea was accepted, request developer permissions for the project via Gitlab. -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. +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. +3. When you have developer privileges you can make branches, check them out, work on them locally, push them back and post merge requests. +4. 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. +5. 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 -- 2.39.2