Development
This section is under construction and more elements will be added over time
This documentation is not a detailed how-to develop IRIS. It gives some insights to help understand the basic code of the project and how to contribute.
General repositories conventions
Branches
We are using the Gitflow Workflow to manage our git branches.
In a nutshell :
master
contains only "production-ready" codedevelop
contains the major development code. When ready it is tagged and merged intomaster
- The sub-branches of
develop
contains either :- A new feature in development, in which case the naming convention is
new_feature
- An issue fixe, in which case the name convention is
iXX_issue_title
, with XX being the issue number
- A new feature in development, in which case the naming convention is
Commits
The commits convention is the following :
- Create commits as small as possible, i.e atomic commits
- If it's not related to an issue, the format
[action] Commit message
is used, withaction
being a 3 letters action related to the commit, egADD
for additions,DEL
for deletions,IMP
for improvements, etc. - If it's related to an issue, prepend with the issue ID, i.e
[#issue_id][action] Commit message
Sections
The following sections are available in this documentation :
- Structure overview : general structure of IRIS code
- Environment setup : guide to setup a development environment
- Coding tips : basic codes hints
- DB migration : things to consider if the code changes the DB schema
- Hooks : an introduction to IRIS hooks
- Modules : a guide to develop modules