If you have a very small to do (typo, doc, one file commit), you’d better use GitHub. You can click edit in the Alignak repository.
It will fork the repository for you and let you edit the file through the Web interface.
Once you picked a good commit message (see below for commit message habits) you can push it in a new branch (see below for branch name habits).
Finally, you can create a new pull request to the Alignak repository (still with GitHub UI)

cdtestspytest--verbose--durations=10--no-print-logs--cov=alignak--cov-config.coveragerctest_*.py# A more simple test run (without verbose and code coverage)pytesttest_*.py# A single testpytesttest_my_tests.py

If you have enabled Travis on your fork (recommended) you will receive Travis notifications about the tests results once you pushed some commits to your repository. Else you should browse the Travis builds on the Travis CI.

You should be ready to commit now, all new files and modified files are added in “stage”. If you look at the commit tree, you can notice more or less a pattern in commit message

Enh|Fix|Add:<Genericwordtodescribe>-<Specificwordtodescribe>

Example:

Enh:Tests-Cleanunusedimports

This is not a mandatory format to write commit. If you want to do it differently it’s fine.
Always keep in mind that a commit message has to be clear enough.
Message like “fix”, “try1”, “update”, “clean” are not really relevant to understand what’s in the commit.