chore: add positive and negative test cases

[massfords]

closes: #165

[massfords]

😞 unsure what the problem is here. This commit lint rule keeps failing.

[OranShuster]

@massfords i think you need to add a blank line in the commit message above the Closes... line

[massfords]

@massfords i think you need to add a blank line in the commit message above the Closes... line

Thanks for the prod. I tried adding a line above the closes but it still failed. However, I noticed that I was getting a warning in the console about the commit rule failing which I hadn't noticed before. I removed that line entirely and it worked.

Maybe I need to keep my commits messages to a single line?

Anyway, thanks for the suggestion, it got me to look at this again.

[ChristopheBougere]

Hey, sorry for all the troubles with commitlint :/

The reason why I'd prefer to keep it is that it ensure semantic release can generate proper releases in Github and choose the type of version (major/minor/patch) depending on what's included. I could also remove commitlint and always squash and reword the commit, but I find it more risky.

I don't know much how to help you because it always worked pretty well for me, but if keeping your messages to a single line works for you, it can be a workaround...
Otherwise drop me a mail (address on my profile) and we can try to debug it live.

Thanks for the contribution anyway!

[github-actions]

🎉 This PR is included in version 3.12.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀