1Contributions to the Cogent repository are welcome!
2
3To keep the license rights for this projects clear, we require a Contributor
4Licence Agreement (CLA) for all contributions.
5
6The Licence agreement certifies:
7  * That you have the rights to give us the contribution, and
8  * That you give us the rights to use your contribution
9
10Please sign the [Contributor License Agreement](http://ssrg.nicta.com.au/projects/TS/cogent.pml#contrib), scan it and send it to us at
11*cla AT trustworthy.systems*
12
13For this repository, we can review pull requests directly on github if we have a
14signed CLA on file, no need to email a patch.
15
16If you have only small trivial changes such as style, typos, comments, or white
17space and don't want to sign a CLA for that, please file an issue in the github
18issue tracker, we'll usually be happy to do the change for you and attribute
19your idea by linking to the github issue in the change set comment.
20
21
22Git conventions:
23* Commit subject line starts with a short tag, indicating the area of the work. E.g.
24  `compiler`, `doc`, `c-refinement`, `ci`, `bilby`. These are not predefined; you can
25  make up new ones as long as they make sense.
26* Refer to the relevant GitHub tickets, if any.
27* Use a `[skip ci]` tag (see: https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build)
28  in the body of the commit message (not in the subject line), if your changes don't
29  require the Travis regression test.
30* Use a `[skip lemma]` tag in the body of the commit message, if your changes don't involve
31  Isabelle/HOL specifications and proofs.
32* Don't worry if you are unsure what to put. We'll amend the messages accordingly when we
33  "merge" pull requests.
34* Don't `merge`. We prefer a linear history with `git rebase`.
35