Add pages on best git workflows and practices?

[signekb]

Maybe we could benefit from having explicit best-practice guidelines for e.g., good commit messages, issues, prs?

• Specifically, when to create issues and pr's, standards for issue/pr naming and commit messages (e.g., prefixes like fix, feat, style, refactor, test, etc.?).
• We could also include issue templates? + issue guidelines entry
• Add linters (and the like) to install and use
• Pre-commit hooks? Md checks in doc repos?
• Test development guidelines?
• Automatic deletions of branches after merge?

I think this would also be helpful for the Onboarding page.

If you agree, I can spend some time writing drafts for these pages.

[lwjohnst86]

Yes! Completely agree, it's been on my to-do list. If you want to start something, that would be fabulous!

[signekb]

Great! Will give it a go after my vacation 👍

[lwjohnst86]

Just linking this reference here on using the slash within git branches to separate things: https://code.erpenbeck.io/git/2021/03/01/git-naming-conventions/

[lwjohnst86]

related to commit messages: https://www.conventionalcommits.org/en/v1.0.0-beta.2/

[signekb]

Yep, have looked at conventional commits. Should I write that up as the recommended convention for commit messages?