Austin Kettner austinkettner

Git Commit Message Model

Capitalized, short (50 chars or less)
DO NOT reference Github Issues via Resolve #24, etc. This is Github specific functionality and clutters the log with non-referenceable data.
Always use present-tense, imperative-style writing
Avoid commits covering multiple changes, always commit frequently to cover specific changes
In any advanced changes ALWAYS include a detailed git commit message in the description/body (explaining the short summary).

	<a class="item btn-icon" href="/Item/Info/Baseball-Tickets-Nationals-at-half-price/3923" data-id="3923" title="Baseball Tickets (Nationals) at half price">
	<div class="box">
	<div class="fav-box"><span class="op-login-active icon icon-fav" data-id="3923"></span></div>

	<div class="preview">
	<img src="http://static.openmarq.com/up/2664c0ccb9b34f39894f013621591202/b9c52debf312443a9e3bf7751c3544ca.jpg" alt="Baseball Tickets (Nationals) at half price">
	</div>

	<div class="info">
	<h3>Baseball Tickets (Nationals) at half price</h3>

	module Sparq::Mail::Formats

	class Welcome

	message = File.read("layout.slim")
	end

	class VerifyEmail

	end

	---
	title: Work
	layout: page
	isPage: true
	pageOrder: 2
	---

	h2 Work
	p A full log containing all my work is coming soon!

	# Combine All Files in Folders to one folder**
	find . -type f -print0 \| xargs -0 -I file mv file .