feat: introduce proper commit linting

[temideewan]

Closes #172

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: temideewan / name: temidayo (833d0d5, 8077b32, 5d4584d)

[JamieSlome]

@temideewan - make sure to review and sign the EasyCLA 👍 This is a requirement before we can merge your PR...

[JamieSlome]

@temideewan, can you please merge in the latest remote changes from this repository, so we can get the vulnerability scan to run before we merge?

[temideewan]

Hi @JamieSlome
I don't think anything has changed since when I created a fork of this repository

[JamieSlome]

@TheJuanAndOnly99, is there any reason the CVE checks aren't running on this PR?

[TheJuanAndOnly99]

@JamieSlome Strange. Looking into it. Will get back to you as soon as I find something.

[TheJuanAndOnly99]

@JamieSlome @temideewan The action is set to trigger only on "push". I've just sent a PR that would add the trigger on "pull_requests" as well. I'm not sure if it will make it run on this PR however. If it doesn't we may need to close it and re send it.

[JamieSlome]

@temideewan, are you able to close and re-open the PR?

[TheJuanAndOnly99]

@JamieSlome @temideewan I don't think we need to close. I re ran the actions and the CVE scan is working + passing!

[temideewan]

Okay so it can be merged yeah?

I'm really excited contributing to this.

[JamieSlome]

LGTM! 🍰

[JamieSlome]

@temideewan - for some reason, the checks aren't running for me. Do you get a successful linting when you try to commit?

[temideewan]

Yes I do.
That's weird.
I'm following up on some threads about it here on GitHub though

[temideewan]

Hi @JamieSlome
Since I can't replicate the issue on my end can you try any of the suggestions from this stack overflow thread?