feat(ci): release & commitlint workflows

[rojvv]

• Initialized commitlint workflow to enforce the Conventional Commits style for commit messages.
• Initialized release workflow to creat releases with automatically-generated release notes on tag creations.
• Updated the versions for actions/checkout.

[KnorpelSenf]

Running it on push is fine. IMO a major advantage of this is that we can generate release notes automatically and add GitHub releases whenever a new tag is created on main. Is it possible to add this?

[rojvv]

Yes, it is.

[rojvv]

But wait.

[KnorpelSenf]

With what?

[rojvv]

It will run 2 times for a pull request coming from the same repository (this repository). Should we do it on push only for main?

[KnorpelSenf]

How about using the same as

grammY/.github/workflows/deno.yml

Lines 11 to 15 in ee990d4

	on:
	push:
	branches: [main]
	pull_request:
	branches: [main]

?

[KnorpelSenf]

automatically and add GitHub releases whenever a new tag is created on main

Do you want to do this here, too?

[rojvv]

Should I?

[KnorpelSenf]

I think that would make sense, yes. For me, that's the main point of the formats. Readability may also get better, but I must admit that this isn't typically an issue.

[rojvv]

Thanks for the article you wrote on your opinions. I thought that I might think of doing both of them here, and I came up with the consequence that I should.

[KnorpelSenf]

Thanks! Let's hope this works 😄