Eric Holmes

I was imaging it would just be a separate control layer in `package server/slack`. It'd just be a consumer of `package empire` like the api is. I think this could...

Thanks for reporting! We [don't do anything weird](https://github.com/remind101/empire/blob/master/Makefile#L53) when building a release binary, so I'll have to dig into why we're not getting a statically linked binary.

A good first step for this would be to capture CTRL-C and show a message that indicates that it's not cancelling the deployment.

Hmm, this actually shouldn't be a problem, right? If you're on master, then it's going to create the deployment using the `master` ref and get resolved on GitHub, which will...

Yeah, it'll use the master ref if you're using v0.0.2.

Yeah, that would be nice. It's pretty easy right now to push a commit, then deploy before the new HEAD actually registers on github. Could probably use the [GET /repos/:owner/:repo/git/refs/:ref](https://developer.github.com/v3/git/refs/#get-a-reference)...

Ah yeah, that's definitely a legit bug. If you specify a repo on the command line, we shouldn't fallback to git.

Could shell out to `open` on OS X if a flag is provided. In iTerm, you can also `Command` + `Click` and it'll open the link.

Good point. Having Honeybadger as the default backend is probably a little too opinionated. The raiser backend isn't great because you can get into scenarios where it loops infinitely with...

Thanks for the suggestion! I'll definitely update the readme. Regarding the `backend: :raiser`, I'm hesitant to add things like this because it adds complexity, and makes things less explicit. It's...