Editing Git Branch Naming Conventions

== Overview ==

Guidelines for Git branch naming conventions

== Working Model ==

I am mostly basing this on the Stackoverflow article in the [[#Reference]] section below.

=== Project tracking system ===

For now, assuming that Trac is the project tracking software. Changes are logged as "tickets". Branches should incorporate the tracking id found in Track: "T" + tracking id, e.g. "T0010".

=== Git branch naming conventions ===

Break the Git branch name down to "GROUP/

=== Commit messages ===

<syntaxhighlight lang="bash">
$ git log --oneline --decorate
</syntaxhighlight>

The above command will list all commit messages along with the active branches that they are associated with. If a branch has been deleted it will not be displayed with `git log`.

Therefore, when making commits it's best to lead with the branch name. While the branch is active the lines from `git log` will contain redundancies, but later on after a branch has been retired the commit message can be used to audit commits. 

<syntaxhighlight lang="bash">
$ git log --oneline --decorate
</syntaxhighlight>

== Reference == 

* [http://stackoverflow.com/questions/273695/git-branch-naming-best-practices|StackOverflow: Git Branch Naming Best Practices]
* [http://nvie.com/posts/a-successful-git-branching-model/|nvie.com: A Successful Git Branching Model]

[[Category:Web_Development]] [[Category:Git]]