Pierre Vanduynslager

> I guess supporting a simpler setup where all packages are released with the same version like in https://github.com/pouchdb/pouchdb should be much easier to support, right? There is no simple...

The tag is pushed to the remote between the `prepare` and `publish` steps because some plugins, such as `apm` require to have the tag on the remote. For example, when...

That wouldn't solve the problem as some platform might not provide a good way to figure out what was the last version released. In addition that would create a huge...

Another solution to explore would be to offer users the possibility to run locally `semantic-release recover ` which would be interactive and allow them to choose each `publish` plugin if...

@mike-north see https://github.com/semantic-release/npm/issues/11 and https://github.com/semantic-release/npm/issues/93. I'm also working on a solution that would allow to publish npm package with 2FA enable for publish. The solution would to publish to a...

The namespace should be added [here](https://github.com/uxsolutions/bootstrap-datepicker/blob/master/js/bootstrap-datepicker.js#L1524) as well.

The same issue happen with the rule `require-jsdoc` that is part of `eslint` core. I don't know if this new behavior of `eslint` is intentional or not.

The reason is that I mostly based the code on the GitHub behavior. In GitHub `fixes #18, #19` applies the `fixes` keyword to `#18` but not to `#19`. Can you...

Thanks for those info! So it seems keywords have to be applied to each issue reference that are separated by `,` or `and`. Doing that would be a big rewrite...

Hello, is there any plan to merge this PR? It would be really useful. Thanks