Update CHANGELOG Format and PR Title Formats

[thw26]

https://keepachangelog.com/en/1.0.0/

Per brief comment exhcange with @ctrlaltf24, we should look to standardize our changelog as well as the titles for PRs.

[ctrlaltf24]

A standard for commit message format that I normally use: https://www.conventionalcommits.org/en/v1.0.0/

[n8marti]

A standard for commit message format that I normally use: https://www.conventionalcommits.org/en/v1.0.0/

This looks like a nice idea, although I maybe would end up incorporating a lazy version of it. But these all look doable to me:

types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.

[n8marti]

https://keepachangelog.com/en/1.0.0/

Per brief comment exhcange with @ctrlaltf24, we should look to standardize our changelog as well as the titles for PRs.

This looks good to me, too, but I haven't yet been involved in updating the changelog. I guess I could start...

[n8marti]

We could broaden this out and include standardizing on linting? Or maybe that's already semi-official with ruff?

[n8marti]

Is there a PR title format suggestion already?

[ctrlaltf24]

there a PR title format suggestion already?

Same format as commit message

[ctrlaltf24]

We could broaden this out and include standardizing on linting? Or maybe that's already semi-official with ruff?

Created a new issue #287

[ctrlaltf24]

incorporating a lazy version of it

Perfectly fine with this, no need to be strict but having a standard format could help our commit messages and changelog be more readable across authors. So what if we slip up a little bit, or our changelog format uses different markdown formatting. For the changelog what's important is the methodology - that this is meant for users (with links to GitHub), but is meant to be readable on its own.