Move to @conventional-commits-rs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 101
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
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.io
- Some kind of changelog generator.
Almost 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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. The issue describes a planned move of this Rust crate to @conventional-commits-rs after the linting tool is implemented; confirm the migration plan and repository ownership before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100