kr/heroku-buildpack-go — pull request #11 by mmcgrana (2012-09-17 21:39:02+00:00)
Title: Normalize messaging

This changeset normalizes and streamlines the messaging emitted by the Go Buildpack:

* Consistently use `----->` for action headers, no prefix for minor actions, and ` ! ` for errors.
* Consistently use `... done`
* Print the exact command used to build the app, which should be the exact command the user is using locally.
* Elide output from installing Python, Mercurial, and Bazar.
* Don't message about Python, Mercurial, or Bazaar at all after successfully installed.
* Update the readme to reflect current state of the buildpack.

Example output:

```
$ git push git@heroku.com:test-go-buildpack.git master
-----> Heroku receiving push
-----> Fetching custom git buildpack... done
-----> Go app detected
-----> Installing Go 1.0.2... done
Installing Virtualenv... done
Installing Mercurial... done
Installing Bazaar... done
-----> Running: go get ./...
-----> Discovering process types
Procfile declares types -> web, worker
-----> Compiled slug size is 1.8MB
-----> Launching... done, v4
http://test-go-buildpack.herokuapp.com deployed to Heroku

$ git push git@heroku.com:test-go-buildpack.git master
-----> Heroku receiving push
-----> Fetching custom git buildpack... done
-----> Go app detected
-----> Using Go 1.0.2
-----> Running: go get ./...
-----> Discovering process types
Procfile declares types -> web, worker
-----> Compiled slug size is 1.8MB
-----> Launching... done, v5
http://test-go-buildpack.herokuapp.com deployed to Heroku

$ git push git@heroku.com:test-go-buildpack.git master
-----> Heroku receiving push
-----> Fetching custom git buildpack... done
-----> Go app detected
! A .godir is required.
! See https://gist.github.com/299535bbf56bf3016cba for instructions.
! Heroku push rejected, failed to compile Go app
```