From 414ef845d6efe811abf9a211d36b0f4a9668d5c2 Mon Sep 17 00:00:00 2001 From: Andrew Dolgov Date: Sun, 16 Jul 2017 20:41:29 +0300 Subject: [PATCH] update CONTRIBUTING.md --- CONTRIBUTING.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 172084f5..15bbce72 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,9 +1,9 @@ ## Contributing code the right way -*or: how I learned to post merge requests without crying myself to sleep* +TLDR: it works pretty much like Github. + +1. Make an account on Gogs +2. Fork the repository you're interested in +3. Do the needful +4. File a pull request with your changes against master branch. -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. \ No newline at end of file