devon blandin

Hey @bodhi, Engines may include vendored plugins and/or shared configurations for use during analysis. I might reference the [instructions](https://github.com/codeclimate/codeclimate-eslint/blob/master/CONTRIBUTING.md#adding-and-upgrading-plugins) we have in the codeclimate-eslint engine, and open a PR here...

We're moving to `v8.4.0` in our cronopio beta channel, so we should be able to close this out soon.

Sounds like a nice feature to me! Not sure when we would have the opportunity to implement this internally but I'll add a couple GH labels to encourage a community...

Hey @aspiers, You should definitely check out http://danger.systems / https://github.com/danger/danger by our friends at @artsy. It has a bunch of cool features including support for commit message analysis.

Still very bad 😬 Hopefully not many people print our blog though...

Hey 👋 This post really speaks to me and I think you should ship it ❤️

Thanks @efueger! @brynary I think we're still blocked until we have the git committed at value available.

Hey @a-b, We've discussed this internally and while we're waiting on Heroku to support this environment variable via Heroku CI, you can use the following (not entirely recommended) workaround: ```...

Hey @dja, you can use the workaround posted in https://github.com/codeclimate/test-reporter/issues/226#issuecomment-335218428. Just be aware that there might be some weirdness rendering data if the generated data and `commited_at` date are significantly...

Hey @dja, It looks like your subshell value isn't excuting correctly. I think that's because you're wrapping the subshell command in single quotes which doesn't trigger interpolation. I'm also wondering...