commit-analyzer
npm
| commit-analyzer | npm | |
|---|---|---|
| 4 | 3 | |
| 340 | 232 | |
| 0.3% | 1.7% | |
| 9.0 | 9.0 | |
| 7 days ago | 2 days ago | |
| JavaScript | JavaScript | |
| MIT License | MIT 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
npm
-
Using semantic-release to automate releases and changelogs
@semantic-release/npm to publish npm packages in a public or private registry
-
Automatically update git major tags on GitHub marketplace release
@semantic-release/npm
-
You don’t need semantic-release (sometimes)
You may need a minor tweak up. For example, push some pkg to both public and internal registries. Ooops. "...publishing to two different registry is not a good idea". In this case you can not rely on stable, convenient and tested in millions runs semrel/npm plugin, and you have to just write a pair of commands by hand with semantic-release/exec instead:
What are some alternatives?
action-semantic-pull-request - A GitHub Action that ensures that your PR title matches the Conventional Commits spec.
semantic-release-monorepo-hooks - Workarounds to handle `semantic-release-monorepo` multipublishing
semantic-release - :package::rocket: Fully automated version management and package publishing
exec - :shell: semantic-release plugin to execute custom shell commands
changelog - :blue_book: semantic-release plugin to create or update a changelog file
npmlog - The logger that npm uses
execa - Process execution for humans
semantic-release-toolkit - Semantic release tools, plugins and configs for QIWI OSS projects
semantic-release-conventional-config - semantic-release shareable config to publish to npm and/or ghcr
semantic-release-docker - semantic-release plugin to build and push docker images
npm-install - GitHub Action for install npm dependencies with caching without any configuration
Reg2CI - Create System Center Configuration manager ConfigItem (CI's) from a .reg (Registry) or a .pol (Policy) file.