cargo-crate-api
committed
| cargo-crate-api | committed | |
|---|---|---|
| 3 | 5 | |
| 7 | 96 | |
| - | - | |
| 8.5 | 7.9 | |
| almost 2 years ago | 12 days ago | |
| Rust | Rust | |
| - | 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.
cargo-crate-api
-
Implied bounds and perfect derive
As for detecting this, the cargo team has been maintaining documentation on crate semver compatibility (which is similar but not exactly the same as the stdlib) and we've been finding we want to switch to automating this instead. We are looking at adopting my proof of concept. I've been meaning to get it setup for a bigger request-for-contributors but haven't gotten to it yet.
-
Cargo: Namespaced and weak dependency features have been stabilized
cargo-crate-api
-
[Gitoxide December Update]: a new object database and upcoming multi-pack index support
cargo-crate-api checks out a ref to an arbitrary directory. It chooses the latest tag if one wasn't specified
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
What are some alternatives?
rust-semverver - Automatic checking for semantic versioning in library crates
auto-changelog-action
rust-crates-index - Rust library for retrieving and interacting with the crates.io index
onefetch - Command-line Git information tool
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
really-small-backpack-example - A really small example of the Backpack module system for Haskell
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
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 ⛰️
git-stack - Stacked branch management for Git