Grzegorz Rajchman mrliptontea

Sublime Text 3 - Useful Shortcuts (Windows)

Good commit messages serve at least three important purposes:

To speed up the reviewing process.
To find out what changed in a range of commits (e.g. for a release note).
To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.

Structure your commit message like this:

	#!/bin/bash
	# ------------------------------------------------------------------
	# Git Daily Scrum (stand-up meeting) helper.
	#
	# The script helps you remember what you did last time and facilitates
	# writing daily log for remote teams. Be aware that it assumes that
	# meetings are conducted at the same time every day.
	#
	# Installation:
	# 1. Place the script in some folder, e.g. your home:

	/**
	* ------------------------------------------------------------------
	* Get notified when you should run some commands when switching
	* between branches.
	*
	* Usage:
	* Adjust `checkChange` function calls by putting a command as
	* the second argument, and then a list of file/folder paths
	* that you want to monitor for changes as following arguments.
	*