Document pull requests, branching and code style

This commit is contained in:
Tuncer Ayaz 2011-05-21 09:59:20 +02:00
parent ea8aca4519
commit fd417ee873

View file

@ -46,13 +46,29 @@ Clone the git repository:
Contributing to rebar Contributing to rebar
===================== =====================
Coding style Pull requests and branching
------------ ---------------------------
Use one topic branch per pull request.
Do not commit to master in your fork.
Provide a clean branch without any merge commits from upstream.
Usually you should collapse (squash) any intermediate commits into the original single commit.
Code style
----------
Do not introduce trailing whitespace. Do not introduce trailing whitespace.
Do not mix spaces and tabs.
Do not introduce lines longer than 80 characters. Do not introduce lines longer than 80 characters.
[erlang-mode (emacs)](http://www.erlang.org/doc/man/erlang.el.html) indentation is preferred.
If you prefer vi, consider extending emacs with [Vimpulse](http://www.emacswiki.org/emacs/Vimpulse).
Writing Commit Messages Writing Commit Messages
----------------------- -----------------------