diff options
author | Andrew Dolgov <[email protected]> | 2017-04-23 22:19:14 +0300 |
---|---|---|
committer | Andrew Dolgov <[email protected]> | 2017-04-23 22:19:14 +0300 |
commit | 1ca6115e388621ad33787a7933434d44cb1de222 (patch) | |
tree | adcbbcc8ebd31bd8fe1f5b20d2173f8898556729 | |
parent | d468256d0f6c61114331da49209029d6b301c124 (diff) |
fox deleted page: HowToContribute
-rw-r--r-- | HowToContribute.md | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/HowToContribute.md b/HowToContribute.md deleted file mode 100644 index e19fc2b..0000000 --- a/HowToContribute.md +++ /dev/null @@ -1,20 +0,0 @@ -## Contributing code the right way - -*or: how I learned to post merge requests without crying myself to sleep* - -1. Post your brilliant idea on the forums, ask to be given developer privileges. Preferably post diffs if you got them. Don't forget to mention your gitlab username. -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. - -You can see an example of the workflow [here](https://tt-rss.org/forum/viewtopic.php?f=10&t=3609&p=21462#p21461). - -Questions? Here's the [gitlab-related thread](https://tt-rss.org/forum/viewtopic.php?f=10&t=3432) on the forums. - -## How to contribute the wrong way - -https://tt-rss.org/forum/viewtopic.php?f=8&t=3605 - -## Is there a code of conduct? - -Yes. If you can help it, don't be an idiot baby.
\ No newline at end of file |