ci(travis): include commitlint stage

[myii]

• https://github.com/conventional-changelog/commitlint
  • Lint commit messages.
  • Ensure that they are in accordance with semantic-release settings.
  • Use Travis CI to display errors and prevent release stage if so.
• https://conventional-changelog.github.io/commitlint/#/reference-rules
  • Specific rules are defined in commitlint.config.js.
  • Using the default rules at the time of this commit.
  • This link gives full details on the default values and how to
    provide custom settings.

---

Notes follow in comments below.

[myii]

With stages set, any failure in a previous stage, cancels all of the following stages.

Originally had this set up as: commitlint => test => release. However, since the main tests are crucial, those have been put first and the commitlint errors can be checked before preparing the actual release. That's the usual time that a rebase might take place with a PR, so the right time to fix the commit messages.

[myii]

IMO, this needs to be merged in before #38 -- that can be rebased afterwards.

[getSurreal]

I was reviewing the commit conventions and was wondering what qualifies as a chore?

build
ci
chore
docs
feat
fix
perf
refactor
revert
style
test

[myii]

@getSurreal You and everyone else! It is a little confusing.

Anyway, have a look at the table in the CONTRIBUTING file. Basically, these are "bot" or "system" tasks that take place automatically, such as when it calculates the version number bump and updates all of the files automatically.

[myii]

@javierbertoli @aboe76 I'm going ahead and merging this because I've got a backlog of PRs to submit. This particular PR is not introducing anything major and will be easy to revert in the event of issues.

[saltstack-formulas-travis]

🎉 This PR is included in version 0.3.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀