MAINT: Create commit guidelines

[Krzmbrzl]

No description provided.

[Kissaki]

We will probably have more guidelines, so I would rather put them into a subfolder for that?

docs/contribution-guidelines/? docs/project-guidelines?

[Kissaki]

I think it is worth establishing context and goals as in describe how features will have multiple commits and then a PR and (equal) merge commit with summarizing the changes as a whole.

[Kissaki]

Missing secondary footer (functionality) like

Co-Authored-By: Author <author@example.com>

[Krzmbrzl]

We will probably have more guidelines, so I would rather put them into a subfolder for that?

Yes I thought so as well but as long as we don't have additional files (nor a CONTRIBUTE.md) I thought it might be best to place it somewhat visibly in the project's root.

I think it is worth establishing context and goals as in describe how features will have multiple commits and then a PR and (equal) merge commit with summarizing the changes as a whole.

I agree on the PR side, but I think a new feature should only be a single commit. You might have previous commits that e.g. refactor the code base in the way you need for the feature but these would be covered by our commit guidelines as well...

[Kissaki]

Having seen the TYPE prefix on commits now I like them.

[Krzmbrzl]

Does someone still have something to add to the guidelines? Or something that you think needs to be changed?

[felix91gr]

I feel you've done a great job! Making decent guides is no easy task, and this one feels pretty good to me :)

[Krzmbrzl]

@felix91gr all done (I think) :)

[felix91gr]

LGTM

I left a small feedback on the Summary comment because I didn't explain myself well yesterday, but otherwise I think this is a-okay :)

[Krzmbrzl]

Ah okay now I understand. I was thinking you were referring to writing summary with a capital letter :)
I also added the code-formatting to Message Body and Footer ☝️