|author||Robin Stocker||2014-07-19 04:59:12 +0000|
|committer||Chris Aniszczyk||2014-07-20 21:44:53 +0000|
It contained outdated information about attaching patches to bug reports. Shorten it to the essentials. Also format it using markdown and rename it to CONTRIBUTING.md, which is a convention and doesn't include "patches" in the name. Change-Id: I9ee73f16e6fa8fbf529ac0ca791e2375d4d56d68 Signed-off-by: Robin Stocker <email@example.com>
Diffstat (limited to 'CONTRIBUTING.md')
1 files changed, 44 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
@@ -0,0 +1,44 @@
+Please refer to the contributor guide for all the details:
+For anything other than small changes, it's a good idea to open a bug
+report for it (in case one doesn't already exist). This gives others the
+chance to give input and is useful for tracking. Create one here:
+We use Gerrit to review all changes by committers or contributors before
+they are merged:
+Make sure you have an account and have set up the `commit-msg` hook
+When committing your changes, see the contributor guide or other commits
+on what your commit message should include.
+Run the following to push your change for review (with `username`
+replaced by your Gerrit username):
+ git push ssh://firstname.lastname@example.org:29418/jgit/jgit.git HEAD:refs/for/master
+Add the link to the review as a comment on the bug report, so that
+people coming from the bug report can find it.
+Then wait for someone to review your change. If there is something to be
+corrected, amend your commit and push it again.
+Have fun :).