chronicle
conventional-changelog
chronicle | conventional-changelog | |
---|---|---|
2 | 12 | |
43 | 7,575 | |
- | 0.8% | |
8.5 | 9.0 | |
4 days ago | 5 days ago | |
Go | 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.
chronicle
-
Git log is not a changelog
we use https://github.com/anchore/chronicle to generate release notes in a changelog format using the issues and PRs from GitHub as the source of truth. In this way time well spent in the curation of issues and PRs (which is something we need to do anyway) means that we automatically get release notes for free. (disclaimer: I'm the author of chronicle)
-
Keep a Changelog
The approach I like to take is to curate issues and PR with semantic titles and organize them by label ("bug", "enhancement", etc) or linking PRs to an already curated issue. This way automation can use these to generate the changlog for me on each release based on closed issues and unlinked PRs since the last release.
We wrote Chronicle to do that automation for us: https://github.com/anchore/chronicle .
The nice thing about this... since you typically curate issues during the development process anyway, if you're doing that right then you get a nice looking changlog for free! We use this approach with our core tools, Syft and Grype (some changlog examples: https://github.com/anchore/syft/releases/tag/v0.31.0 and https://github.com/anchore/grype/releases/tag/v0.26.1 ).
Always happy to hear new feature ideas and possible customizations for Chronicle (put in an issue and let's chat )!
conventional-changelog
-
Git commit helper: add emojis to your commits
Using Conventional Commits โญ as a standard for your commit messages, makes Semantic Versioning ๐ as easy as can be, with tools like Conventional Changelog ๐ Standard Version ๐ and Semantic Release ๐ฆ๐
-
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.
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
semantic-pull-requests
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
chyle - Changelog generator : use a git repository and various data sources and publish the result on external services
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications โฐ๏ธ
jrnl - Quick and easy CLI journaling tool for Github wiki journals.
Release It! ๐ - ๐ Automate versioning and package publishing
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
release-please - generate release PRs based on the conventionalcommits.org spec
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo