will consider if I have time. Right now I am thinking of writing a tool that would configure all project-related services: travis, semantic release, david dependencies, codacy in a single command.

That sounds awesome! And if you're willing, I'd love to help.

Thanks!Ari

On Sun, Aug 23, 2015 at 2:17 PM, Gleb Bahmutov notifications@github.com
wrote:

will consider if I have time. Right now I am thinking of writing a tool that would configure all project-related services: travis, semantic release, david dependencies, codacy in a single command.

Reply to this email directly or view it on GitHub:
#65 (comment)

@bahmutov Awesome, thank you!

I don't understand. https://github.com/semantic-release/semantic-release is advertising this as a feature.

Detect breaking changes using your dependents’ test suites: Help out! Implement the dont-break plugin

Oh, no it doesn't. Reading a second time – "Help out!" is supposed to indicate it is an upcoming feature. Thats a bit misleading.

Nevertheless, this would be a deal breaker.

I believe my plugin https://github.com/bahmutov/dont-crack already does that

My question would be how to do this before an accidental breaking change is merged into master, i.e. on a PR? Using plain dont-break works, but will not consider whether the commit messages include BREAKING CHANGE

@bahmutov do you think you could update https://github.com/bahmutov/dont-crack to the latest semantic-release API?
Or maybe someone in the community would like to make a PR for that?
The we could add it to https://github.com/semantic-release/semantic-release/blob/caribou/docs/extending/plugins-list.md#community-plugins