Contributions are appreciated. As a mostly single developer of this project there are too many things that I'd like to do. But I don't have time to implement/fix everything and burnout is a thing. There is a lot of code, some good some bad. Newer code is generally of a better quality.
Generally for smaller stuff it is fine to create a PR with the changes.
Its preferable to create either an Issue, discussion item or draft PR. This is because it is usually better to discuss these before creating a large PR with many changes. Is is also easier for me as a the code owner to be able to groom larger changes.
This repo always squash and merge commits. Therefore, intermediary commits aren't that important. Release please is used to automate releases and changelog. Also see Conventional commits
- Do test things locally first
- Create PR, add relevant description.
- Make sure github tests succeed (some may have to be manually run by code owners)
- Code owners will do a code review.
- Depending on whether the commits use convention commits format, the code owner may modify the commit header and body when merging the PR. Alternatively you can write the changelog entries in the PR description or title.