Files
jami-daemon/CODING
Maxim Cournoyer bf105816ca Small cleanup of the ring-daemon introductory material
* CODING: Update wiki URLs and refresh content.
* ChangeLog: Fix typo.
* README: Likewise, and use HTTPS for URLs.
* doc/README: Rephrase.
* man/README.manpages: Fix typo.

Change-Id: I9d320ae2e5bdfacc84293001f08abb442da35fb5
Reviewed-by: Guillaume Roguez <guillaume.roguez@savoirfairelinux.com>
2018-01-09 13:04:30 -05:00

28 lines
1.1 KiB
Plaintext

= Coding Standards =
Please follow our coding standards when developing:
https://tuleap.ring.cx/plugins/mediawiki/wiki/ring/index.php?title=Libring_-_Coding_Rules
= Gerrit Workflow =
Gerrit is used as a code review tool. It is also the primary Git repository.
Wiki documentation: https://tuleap.ring.cx/plugins/mediawiki/wiki/ring/index.php?title=Working_with_Gerrit
== Commit Messages ==
Indicate the number of the related Tuleap issue in your commit message.
== commit-msg hook ==
The Gerrit commit-msg hook must be installed before code reviews can be pushed to Gerrit.
This is because Gerrit relies on a unique Change-Id that can be tracked. The commit-msg hook
takes care of inserting a Change-Id in your commit messages for you.
It can be installed in your local git repository with the following command:
$ gitdir=$(git rev-parse --git-dir); scp -p -P 29420 username@gerrit-ring.savoirfairelinux.com:hooks/commit-msg ${gitdir}/hooks/
== Gerrit integration with Jenkins ==
* http://strongspace.com/rtyler/public/gerrit-jenkins-notes.pdf
* https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger