-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Move to @conventional-commits-rs #38
Comments
Thanks for the hard work! What's the status on @conventional-commits-rs? I'm having some trouble finding a good rust commitizen tool and would love to see this one get some love :) Thanks! |
University took most of my freetime up :( I hadn't really time to pick up the project again. Most of the stuff I program are assignments or tools to help me with assignments haha. I'd be happy to get some help though! The parser has some smaller bugs. Might be worth thinking about moving to a grammar based one with pest for example. The changelog generator is quite simplistic as well. It generates the whole document over again instead of parsing the existing one and doing a diff. This has some drawbacks. Manual editing is not possible for example. I do have a month free, starting mid September. Ivr already put the org on the top of my to-do list. I nerd the tools myself. I do use the existing ones. But they're buggy sometimes and not really user friendly right now. |
Can we help in some ways? Because it seems an interesting and useful project :) |
Hey!
Quick update on the future of this crate. I am in the process of building the conventional commits ecosystem over at @conventional-commits-rs for Rust based on already existing crates by forking them if unmaintained or complete new re-writes if that improves ergonomics and code quality.
Currently on the plan are:
commitlint
, a simple commit linting tool. Can be used to verify that your commit matches organization-specific settings.cargo-semantic
, a cargo plugin used to create semantic releases. It automatically detects the changes and runs checks, tests, pushes the new tag and publishes to crates.ioAlmost done are some generic utility crates for parsing and type definitions.
This repository will move in the near future over to the organization once I have implemented the linting tool. This puts all related crates into one place, allow for easier collaboration and (hopefully!) keep the fully automated release toolbox dream alive!
Cheers!
The text was updated successfully, but these errors were encountered: