-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: conventional commits #82
Comments
conventional commits
feature is good idea
I was just thinking of building something but didn't want to add more fragmentation here. For a nice example of what I've found: https://github.com/SKalt/git-cc @chriswalz would you be up for a contribution to add Would much rather see extensibility with Bit vs adding more tooling here. Also if so, any quick 101 bullet list on where the best place is for contributing something similar would be? |
I think would be nice! Do you think could outline the usage of commands here (e.g. `bit cc <> does A, bit cc does B, etc..) See my notes for getting started adding a command here Regarding a config file I've been avoid that and leaning on ENV variables for now. We could hard code a config as a first pass and then find a way to best handle config file solution once the |
Sweet! For the first go round, it could just be the standard allowed commits by the Angular Conventional Commit format and that would be a good iteration one to see how it works out. Command draft
Here's another from git-cz resources |
Looks good to me. I think you should go for it! If you get stuck I'll be happy to help out! |
https://www.conventionalcommits.org/
https://github.com/brigand/glint
The text was updated successfully, but these errors were encountered: