Marc Kassay marckassay

Commit Message Format

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

Commit Message Conventions

These rules are adopted from the AngularJS commit conventions.

Goals
Generating CHANGELOG.md
- Recognizing unimportant commits
- Provide more information when browsing the history
Format of the commit message
Subject line

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

	/**
	* This gulpfile will copy static libraries and a index.html file as well as
	* merge, babelify and uglify the rest of the javascript project.
	*
	* TODO:
	* - Separate media, libs and src with different watchers.
	* - Media and libs should only be copied to dist if they are different sizes.
	*
	* The expected project is to be laid out as such:
	*

	function Invoke-Process
	{
	[OutputType([PSCustomObject])]
	[CmdletBinding()]
	param
	(
	[Parameter(Mandatory = 0, Position = 0)]
	[string]$FileName = "PowerShell.exe",

	[Parameter(Mandatory = 0, Position = 1)]