As minus is continuously growing in size along with new contributors and users, it is essential to have proper standards for all the important aspects of the project.
minus is written in Rust, and the Rust Community has already defined
a good set of rules for codebases written in Rust and minus also blindly follows these rules.
But one such area where minus lacks a good standard is Git commit messages. Although the CONTRIBUTING.md file describes a format for commit messages, it isn't thorough enough to be imposed as a standard.
To improve the quality of commits, minus will now officially switch to Conventional Commits v1.0.0 and all commits from now on will be strictly under Conventional Commits v1.0.0. Contributors are also required to write their commit messages that follow Conventional Commits v1.0.0.
There are some pre-requisites that should be clearly converted before this issue can be enacted upon.
[x] Clearly define the scopes. Also describe all the types that can be used.
As minus is continuously growing in size along with new contributors and users, it is essential to have proper standards for all the important aspects of the project.
minus is written in Rust, and the Rust Community has already defined a good set of rules for codebases written in Rust and minus also blindly follows these rules.
But one such area where minus lacks a good standard is Git commit messages. Although the CONTRIBUTING.md file describes a format for commit messages, it isn't thorough enough to be imposed as a standard.
To improve the quality of commits, minus will now officially switch to Conventional Commits v1.0.0 and all commits from now on will be strictly under Conventional Commits v1.0.0. Contributors are also required to write their commit messages that follow Conventional Commits v1.0.0.
There are some pre-requisites that should be clearly converted before this issue can be enacted upon.
Additional Links