committed
precious
committed | precious | |
---|---|---|
5 | 5 | |
94 | 64 | |
- | - | |
7.9 | 8.4 | |
3 days ago | 11 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
committed
-
Any good alternative to husky in rust to enforce and write conventional commits and for pre-commit source code linting??
I use https://github.com/crate-ci/committed and pre-commit (the python app)
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
committed just reads commit messages between a range of commits, after resolving refs
-
Ouch 0.3.0 released!
For colors, I've found yansi to be great to work with. I then use concolor-control (example) and `concolor-clap (no clap3 support yet, example part 1 and example part 2). As you can see, I also like to organize my colors by the styling role they fill. The only reason I wrapped in that example is its part of the crate's API and didn't want the public API tied to yansi.
-
Git-cliff: generate changelog files from the Git history
While auto-generated changelogs aren't the best, they are better than nothing. Too often I've seen projects without a changelog which is especially annoying when dealing with breaking changes.
I've been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.
If people want enforcement of Conventional Commit, check out https://github.com/crate-ci/committed
- Committed – A commit message linter optionally supporting conventional commits
precious
-
Any good alternative to husky in rust to enforce and write conventional commits and for pre-commit source code linting??
It doesn't do commit message checking but if you want to do linting on commit I wrote a tool called precious. It lets you configure any number of tidiers and linters for your project in a single file. It's written in Rust, but it can be used for projects in any language.
- Show HN: One code quality tool to rule them all
-
All My Perl Modules Are in Maintenance Mode
If you're still using Code::TidyAll, now is a good time to switch to https://github.com/houseabsolute/precious
-
Spellings, Grammer checker for code?
Whilst looking I also found precious which seems to sit over the top of all your other linters and allow you to configure and control them all in one place. Never used it but it looks kind of cool.
-
What I did on my winter vacation
I submitted this here because I discuss a few Rust programs I've created, precious and ubi. I think it's on-topic, but if the mods disagree, I understand.
What are some alternatives?
auto-changelog-action
cargo-husky - Setup Git hooks automatically for cargo projects with :dog:
onefetch - Command-line Git information tool
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
rusty-hook - git hook manager, geared toward Rust projects
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
crates.io - The Rust package registry
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
gnulib - upstream mirror
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️