Git Guidelines

Commit content

Any code deployed to production (be it a web application, mobile application, …) must have been committed into the repository earlier. Commits should deal with one thing (~1 issue) and one thing only. Commit early, polish later.

Commit message

Write an English sentence describing the commit. If a commit deals with an issue from the issue tracker, start the sentence with the issue key.

Example: “#1234 fixing the froboozle”

Branching model

Follow this: http://nvie.com/posts/a-successful-git-branching-model/

No-nos

  • Don’t commit “only at the end of the day”.
  • Never commit a configuration file or any other file that would disclose a password or some secret key.