Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • release/202005
  • release/202001
  • release/201912
  • release/201911
  • release/releaseWindowsTestOne
  • release/windowsReleaseTest
  • release/releaseTest
  • release/releaseWindowsTest
  • release/201910
  • release/qt/201910
  • release/windows-test/201910
  • release/201908
  • release/201906
  • release/201905
  • release/201904
  • release/201903
  • release/201902
  • release/201901
  • release/201812
  • 4.0.0
  • 2.2.0
  • 2.1.0
  • 2.0.1
  • 2.0.0
  • 1.4.1
  • 1.4.0
  • 1.3.0
  • 1.2.0
  • 1.1.0
30 results

CODING

Blame
    • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    CODING 1.09 KiB 
    = Coding Standards =

Please follow our coding standards when developing:
https://git.jami.net/savoirfairelinux/ring-project/wikis/guidelines/Libring-coding-rules

= Gerrit Workflow =

Gerrit is used as a code review tool. It is also the primary Git repository.
Wiki documentation: https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/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