jbampton opened a new issue, #2762: URL: https://github.com/apache/sedona/issues/2762
"The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with [SemVer](https://semver.org/), by describing the features, fixes, and breaking changes made in commit messages." https://www.conventionalcommits.org/en/v1.0.0/ I find that the pull request template could be improved. A lot of the time the only choice is to mark stuff as `[DOCS]` when a lot of the time it really is something else. https://github.com/apache/sedona/blob/master/.github/pull_request_template.md So this task if approved would be to also update the contributing guides and pull request template etc ### Why Use Conventional Commits - Automatically generating CHANGELOGs. - Automatically determining a semantic version bump (based on the types of commits landed). - Communicating the nature of changes to teammates, the public, and other stakeholders. - Triggering build and publish processes. - Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
