This is contribution workflow of OBM-Deploy project. You must follow these rules in order to contribute to this project.
This ticket should explain the purpose of the contribution and must provide the following informations :
-
Description of the need in BDD style (As a user, I try to ..., As a user, I want to ...)
-
Full context (OBM version, deploy version (eg. HEAD), GNU/Linux distribution used, infrastructure type (distributed, obm-full, ...), used inventory, ...
-
Description of the encountered problem (Error message - Fonctionnal behaviour) (eg. obm-satellite service doesn't start, postfix maps aren't generated, ...)
-
Reproduction conditions (eg. launch ansible-playbook -i inventory obm.yml --tags opush, use a python3 virtualenv, ...)
Assign the newly created ticket to yourself by the Assign to me button.
To start working on this ticket, using the Start progress button.
-
Go to obm-deploy repo.
-
Click to Fork button to fork the repo.
-
Click to Clone button and clone the forked repo.
$ git clone [the/copied/url]
Every time start working with obm-deploy
you should refresh your local copy
with remote repo:
$ git checkout master && git fetch && git rebase
Each ticket has its own branch to work with:
$ git checkout -b DEPLOY-52
The commit message must reflect Jira ticket title like in following command :
$ git commit -m 'DEPLOY-52 cyrus frontends may not have mupdate process'
$ git push --set-upstream origin DEPLOY-52
Add @achapellon and @tsarboni as reviewers.
Go to Jira and chage the ticket status using Open Code Review button.
Go to Jira and close your ticket using Code review OK button.