chronicle
release-please
chronicle | release-please | |
---|---|---|
2 | 47 | |
43 | 4,245 | |
- | 5.4% | |
8.5 | 8.5 | |
4 days ago | 2 days ago | |
Go | TypeScript | |
Apache License 2.0 | 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.
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 )!
release-please
-
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 📦🚀
-
How to write GIT commit messages
Conventional Commits
-
How to Improve Development Experience of your React Project
We've covered everything about writing well-formatted and structured code without worrying too much about it anymore. The only part we haven't explored yet is linting commit messages. Commitlint will help us here. It allows you to configure any rules you want for the commit message, but we're going to use the Conventional Commits specification, one of the most popular conventions you'll find.
- Release Please
-
TypeScript Boilerplate
Commit Management with Conventional Commits: The Conventional Commits methodology is adopted to maintain a clear and structured record of changes with the help of commitlint.
-
A Gitlab Review Bot Assistant
Validate if the commit titles adhere to the Conventional Commits Specification in Merge requests.
-
Ask HN: Should commit summaries describe the change, or the intent?
Check out https://www.conventionalcommits.org
-
Announcing release-plz v0.3.0
FYI there is already a popular tool that does just this with a very similar name: https://github.com/googleapis/release-please
-
A clean Git history with Git Rebase and Conventional Commits
The feature commit should have a clear defined message - Don't re-invent here - There exists a fairly used and accepted convention called Conventional Commits, so we are going to use that.
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
semantic-pull-requests
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
chyle - Changelog generator : use a git repository and various data sources and publish the result on external services
cz-cli - The commitizen command line utility. #BlackLivesMatter
jrnl - Quick and easy CLI journaling tool for Github wiki journals.
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
semantic-release - :package::rocket: Fully automated version management and package publishing