GitHub Changelog Generator
committed
| GitHub Changelog Generator | committed | |
|---|---|---|
| 3 | 5 | |
| 7,299 | 94 | |
| 0.2% | - | |
| 6.5 | 7.9 | |
| about 2 months ago | 9 days ago | |
| Ruby | Rust | |
| MIT License | 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.
GitHub Changelog Generator
-
Closing a Knowledge Gap: Best Practices for Writing Git Commit Messages
changelog-generator
-
How to Write a Great Git Commit Message
Interesting, I've been using github-changelog-generator [1] for (you guessed it) automatic changelog generation, which adds bug fixes/features to the changelog based on issues and PRs, but sematic-release looks like it might be even more useful.
[1] https://github.com/github-changelog-generator/github-changel...
- Git-cliff: generate changelog files from the Git history
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?
Asciidoctor - :gem: A fast, open source text processor and publishing toolchain, written in Ruby, for converting AsciiDoc content to HTML 5, DocBook 5, and other formats.
auto-changelog-action
grape-swagger - Add OAPI/swagger v2.0 compliant documentation to your grape API
onefetch - Command-line Git information tool
YARD - YARD is a Ruby Documentation tool. The Y stands for "Yay!"
gitoxide - An idiomatic, lean, fast & safe pure Rust implementation of Git
Annotate - Annotate Rails classes with schema and routes info
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
Hanna - RDoc generator designed with simplicity, beauty and ease of browsing in mind
gnulib - upstream mirror
Doctor
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️