Charlike Mike Reagent

I believe it's because of the "asyncness". Why not try to separate them in separate tasks, and they run one task with dependency tasks? Something like that (I'm not sure...

You mean `assemble.data` or `assemble.pages/layouts/partials`? > you need to load the collections/globs inside a task hm.. why? You even don't need a tasks to assemble to work? I believe you...

I understand it's a good thing to be inside, but it should also work and make sense to work outside of the task. That's why I think it's not the...

> As a rule, you should always, always, always make your code as lazy as possible. Totally agree. Let's @Obscuresounds try these things. I'm all for best practices and great...

Written this why you don't have error handlers, maybe that's why you don't have error? Hm. In anyway, you should return at least one of the streams, or set callback...

I don't see why such things should be in the spec at all when we have awesome tooling like `commitlint`, `git-cz`, and a ton of other useful and cool helpers....

Maybe :)

> @wesleytodd Changing is either a `fix` to the existing feature or a new `feat` on top of the existing feature. For me "change" mean _any_ change. Not specifically a...

@bcoe, sure, worth nothing adding it :) Or at least it should be hinted _somehwere_.

> @hung-doan: abbreviation for Breaking-Change but feature ?. I guess that's why we introduced `!` thing... that I still don't like it's place.