git-cliff
conventional-changelog
Our great sponsors
git-cliff | conventional-changelog | |
---|---|---|
33 | 11 | |
7,609 | 7,563 | |
- | 1.2% | |
9.7 | 9.0 | |
about 21 hours ago | 4 days ago | |
Rust | TypeScript | |
Apache License 2.0 | ISC License |
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.
git-cliff
-
Getting Started with CLI tools in Rust using Clap
git-cliff is a terminal tool that can generate changelog from the Git history by using conventional commits, as well as by using regex-powered parsers and you can even change the changelog template itself by using a configuration file. This tool is a great example of text parsing on the terminal and also uses clap_mangen which generates man pages. Useful for anyone who is serious about looking into making a production-ready terminal tool!
- Adding GitHub integration to git-cliff (need opinions/comments)
-
Auto-Generated Customer-Friendly Changelogs
Solutions exist for this. Our company does this with git-cliff. Using conventional commits, any commit labeled with the subject "www" will appear in our public changelog.
-
changelog-gh-usernames: A tool to replace emails in changelogs with GitHub usernames
This was primarily aimed to work with git-cliff to generate changelogs for GitHub releases, since tagging contributors would include them as contributors for the release, while also ensuring structured changelogs thanks to git-cliff. As of now, it requires a few extra steps to get it working with git-cliff, but the integration should be much better once the PR for post-processors is merged.
- git-cliff is being re-licensed under the MIT & Apache 2.0
- Hey everyone, exciting news! Git-Cliff just dropped version 1.0.0! Who else is psyched to try it out? Let's hear your thoughts in the comments! ππ
- git-cliff 1.2.0 is released! (highly customizable changelog generator)
- Hey guys, exciting news! We just released git-cliff v1.0.0! This tool is gonna make your Git experience even better. Make sure to give it a try and let us know your thoughts in the comments. Happy coding! ππ¨π»βπ»π©π»βπ»
-
A new open-sourcing project launches!!! A declarative, compose-based and cross-platform GUI
It's the first time I see someone combining gitmoji with conventional commits (I use the later now for all my project, to generate my changelogs automatically with with git-cliff.)
- GitHub - orhun/git-cliff: A highly customizable Changelog Generator that follows Conventional Commit specifications β°οΈ
conventional-changelog
-
Using semantic-release to automate releases and changelogs
conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.
-
Conventional Commits - Specification for Your Commit Messages
Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog
-
Minor imperfections that shout βbeginner codeβ
Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.
- GitHub Actions can't find built binaries to put them to a release
- FRONT END - LINKS CRIATIVOS E TΓCNICOS
-
Confused about how to get my packages up to `1.0.0` using Lerna / Conventional commits...
I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.
-
Automatically update git major tags on GitHub marketplace release
conventional-changelog-conventionalcommits
-
Keep a Changelog
[1] - https://github.com/conventional-changelog/conventional-chang...
-
What are some good practices for writing changelogs/update notes?
I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.
-
Automated versioning and package publishing using GitHub Actions and semantic-release
@semantic-release/commit-analyzer It determines the type of our release (e.g. major, minor, patch) by analyzing commits with conventional-changelog. semantic-release uses Angular Commit Message Conventions by default.
What are some alternatives?
cocogitto - The Conventional Commits toolbox
keep-a-changelog - If you build software, keep a changelog.
git-cliff-action - GitHub action to generate a changelog based on the Git history
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
changie - Automated changelog tool for preparing releases with lots of customization options
Release It! π - π Automate versioning and package publishing
cargo-update - A cargo subcommand for checking and applying updates to installed executables
release-please - generate release PRs based on the conventionalcommits.org spec
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo
auto-changelog-action
react-hook-form - π React Hooks for form state management and validation (Web + React Native)