actions-tagger
conventional-changelog
| actions-tagger | conventional-changelog | |
|---|---|---|
| 1 | 12 | |
| 128 | 7,574 | |
| 1.6% | 0.8% | |
| 8.0 | 9.0 | |
| 3 months ago | 9 days ago | |
| TypeScript | TypeScript | |
| MIT License | 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.
actions-tagger
-
Automatically update git major tags on GitHub marketplace release
Actions-R-Us/actions-tagger@v2 - updates major tag on release
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?
git - :twisted_rightwards_arrows: semantic-release plugin to commit release assets to the project's git repository
keep-a-changelog - If you build software, keep a changelog.
npm - :ship: semantic-release plugin to publish a npm package
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️
semantic-release-docker - semantic-release plugin to build and push docker images
Release It! 🚀 - 🚀 Automate versioning and package publishing
changelog - :blue_book: semantic-release plugin to create or update a changelog file
release-please - generate release PRs based on the conventionalcommits.org spec
setup-cpp - Install all the tools required for building and testing C++/C projects.
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo