James Talmage

Here is an example where I wish I could have seen every failure: https://github.com/jamestalmage/babel-plugin-detective/blob/master/test/babel-6-test.js#L165 I could not use `deepEquals`, and using `assert` which throws at the first error was annoying...

> And it will for sure confuse users, when tests continue to run after failed assertions We currently **do** continue test execution, and users aren't confused. We are already collecting...

> To clarify, right now we also report the test blowing up? No. Right now we report just the first failed assertions. Anything that happens after that is ignored. It...

I think we should start by exposing the tasks functions, and testing them individually. For all the git stuff, you can just clone from one directory to another (`origin` does...

I think he's asking for the ability to set a config where releases must be performed from the `release` branch.

I tried global installs with both `yarn` and `npm`. With `yarn`, it was broken, worked fine with `npm`.

You wouldn't want to check status by default? Or do you mean just the await completion part?

> Do we really want to wait 1 hour before the module is actually being published? Yep. It's a requirement for publishing AVA. That's a big part of why I...

I think it should await completion by default, but provide a key sequence / prompt you can use to avoid waiting (and a `--skip-ci` flag). If we don't await by...

Nah. You are doing an OSX sanity check before publishing. Also, you might be publishing days after the last CI run, and dependencies might have updated. If you are actually...