commit-analyzer
conventional-changelog
commit-analyzer | conventional-changelog | |
---|---|---|
4 | 12 | |
340 | 7,576 | |
0.3% | 0.8% | |
9.0 | 9.0 | |
6 days ago | about 19 hours ago | |
JavaScript | 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.
commit-analyzer
-
Using semantic-release to automate releases and changelogs
@semantic-release/commit-analyzer to analyze commit messages with respect to conventional commit conventions
-
Automating Tag and Release Generation with Semantic Release and GitHub Actions for Node.js Applications
Semantic Release is a tool that automates semantic versioning and release creation based on the content of changes made to the source code. By adopting this approach, the tool analyzes commits since the last version, automatically determines the version type (major, minor, or patch) based on the changes made, and then generates a new tag and release. This not only streamlines the process but also ensures consistency and accuracy in your software versions. See default release rules.
-
Semantic release to npm and/or ghcr without any tooling
@semantic-release/commit-analyzer - analyzes conventional commits deciding if they are bumping a patch, minor or major release tag
-
Automatically update git major tags on GitHub marketplace release
@semantic-release/commit-analyzer
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?
action-semantic-pull-request - A GitHub Action that ensures that your PR title matches the Conventional Commits spec.
keep-a-changelog - If you build software, keep a changelog.
semantic-release - :package::rocket: Fully automated version management and package publishing
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
changelog - :blue_book: semantic-release plugin to create or update a changelog file
git-cliff - A highly customizable Changelog Generator that follows Conventional Commit specifications โฐ๏ธ
execa - Process execution for humans
Release It! ๐ - ๐ Automate versioning and package publishing
semantic-release-conventional-config - semantic-release shareable config to publish to npm and/or ghcr
release-please - generate release PRs based on the conventionalcommits.org spec
npm-install - GitHub Action for install npm dependencies with caching without any configuration
rn-boilerplate - React native boilerplate with formik, ui kittens, eslint setup, and expo