Eric Crooks crookse

Problem

I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).

Solution

Use ssh keys and define host aliases in ssh config file (each alias for an account).

How to?

Generate ssh key pairs for accounts and add them to GitHub accounts.

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
Once documentation has been written, development should commence, and test-driven development is preferred.
Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
When a feature is being modified, it should be modified documentation-first.
When documentation is modified, so should be the tests.

	#!/bin/sh

	############
	# Usage
	# Pass a path to watch, a file filter, and a command to run when those files are updated
	#
	# Example:
	# watch.sh "node_modules/everest-/src/templates" ".handlebars" "ynpm compile-templates"
	############

	#!/bin/bash

	# This way you can customize which branches should be skipped when
	# prepending commit message.
	if [ -z "$BRANCHES_TO_SKIP" ]; then
	BRANCHES_TO_SKIP=(master develop test)
	fi

	BRANCH_NAME=$(git symbolic-ref --short HEAD)
	BRANCH_NAME="${BRANCH_NAME##*/}"