Git

• Repos in direct production, keep a general devel branch for small changes and tests.
• For greater changes, create public branches named as task referencing Kanboard so commits are tracked on Kanban.
• Always merge branches with no Fast Forwarding
• For projects with versioning and releases, tag the production/stale ones.
• Backups should be automatically tagged as partial for non 100% success backups and success for the full ones.

• We use devel namespace for software development projects and source code public available
• ops namespace is used for IaaC, configurations and other operational stuff, not all repos are publicly available due security concerns.
• bak namespace is reserved for tools automatically pushing backups into git
• shipyard namespace is reserved for docker images

We should find an easy way to deploy client hooks wide.

• Commit message check/format
• Code linting
• check for unsafe data (disclosure)

Currently:

• Logging
• Kanban comment publishin for referring commits to tasks
• Kanban task moved to last columne on branch merge

• Git Workflow
• https://gist.github.com/pandeiro/1552496