chronicle
| semantic-pull-requests | chronicle | |
|---|---|---|
| 1 | 2 | |
| - | 42 | |
| - | - | |
| - | 8.5 | |
| - | 3 days ago | |
| Go | ||
| - | 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.
semantic-pull-requests
-
Keep a Changelog
* outside contributors get familiarized with the practice much faster (imagine getting new contributors to update changelogs)
We recently adopted this practice at Pyroscope and it's been working out pretty well for us [2], I can certainly recommend it.
[0] - https://github.com/apps/semantic-pull-requests
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 )!
What are some alternatives?
release-please - generate release PRs based on the conventionalcommits.org spec
keep-a-changelog - If you build software, keep a changelog.
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
chyle - Changelog generator : use a git repository and various data sources and publish the result on external services
conventional-chang
jrnl - Quick and easy CLI journaling tool for Github wiki journals.
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
ESLint - Find and fix problems in your JavaScript code.
maintainer - :octocat: :man_technologist: :whale: Generate personal daily reports or summary, AUTHORS, CONTRIBUTING, CHANGELOG and so on for GitHub user or repository.