(optionally) force a build before any deploy
Fixed branch selection logic for git deploys

* Before, because the logic was revered (see
  c0e46393c656eac6e47a83f54041457e3c6a6923), a brand new deploy would
  result in assuming that the deploy branch existed when it actually
  did not. This would cause initial deploys to fail.
* This new logic is more concise, more readable, and still backwards
  compatible with ruby 1.8.
Merge pull request #26 from rmm5t/fix-branch-check

Fix branch selection logic for git deploys
Added license declaration to gemspec
Merge pull request #27 from rmm5t/gemspec-license

Add license declaration to gemspec
Added SFTP deployment
Merge pull request #28 from tobiaswerner/master

Add SFTP deployment
Merge pull request #24 from jm3/force-build

(optionally) force a build before any deploy
The default skeleton provided by middleman now omits versions.
Merge branch 'master' of github.com:tvaughan/middleman-deploy

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Remove the `after_build` option. This never made much sense.
Rename to `build_before` and add corresponding command-line option.
work-around a problem with running build in an extension
whitespace clean-up
update tagline and ensure required settings are provided for sftp
remove the --clean command-line option
add that we removed deploy from the after_build hook
bump
some ftp/sftp related clean-ups
sorry but i can't keep up with the number of contributors