auto-changelog-action
By charmixer
committed
Nitpicking commit history since beabf39 (by crate-ci)
auto-changelog-action | committed | |
---|---|---|
1 | 5 | |
68 | 94 | |
- | - | |
0.0 | 7.9 | |
about 1 year ago | 9 days ago | |
Shell | Rust | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
auto-changelog-action
Posts with mentions or reviews of auto-changelog-action.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-05.
-
Git-cliff: generate changelog files from the Git history
We’ve been using charmixer/auto-changelog-action to generate release notes. This action makes nice references to GitHub pull requests. The release notes are attached to a GitHub release by an action. This turns out to be an invaluable reference for SQA and Product Manager for testing and creating customer-facing release notes.
One downside is that we run into trouble with GitHub API rate-limiting.
https://github.com/charmixer/auto-changelog-action
committed
Posts with mentions or reviews of committed.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-14.
-
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?
When comparing auto-changelog-action and committed you can also consider the following projects:
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
onefetch - Command-line Git information tool