cz-cli
standard-version
Our great sponsors
cz-cli | standard-version | |
---|---|---|
31 | 13 | |
16,381 | 7,548 | |
1.1% | 0.7% | |
2.3 | 2.8 | |
30 days ago | 7 days ago | |
JavaScript | JavaScript | |
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.
cz-cli
-
Aider: AI pair programming in your terminal
Adopt a convention like commitizen: https://github.com/commitizen/cz-cli
'typeofchange(scopeofchange): reason for change'
It sort helps force devs to type out more meaningful commit messages.
-
What is a good message and size for a commit?
Commitizen Define a interface to write your commits and automatically and a prefix and a suffix to your message. (and others features not related)
-
Subject-First Commit Messages
Conventional commits are great, especially if you add in commit linting.
Being able to programmatically increment semantic versions and automatically generate relevant changelogs is awesome.
It’s also nice to implement Commitizen[0] for a little hand holding until folks get used to the linting.
I used to care a lot about doing things the way that felt right to me, but now I just want some common standard that is easy for everyone to follow, easy to automate, and easy to verify programmatically.
Things like conventional commits and semantic versioning aren’t perfect, but they are quite good and apply broadly to many use cases with common tooling and conventions.
--
[0]: http://commitizen.github.io/cz-cli/
-
Automating code patterns with Husky
In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.
-
How to set up Commitzen with Husky
Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.
-
Automated release with Semantic Release and commitizen
When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.
-
Does it make sense to write commit messages that include notes to yourself on how the project is going?
I use Commitizen to enforce a strict commit message. It's not required - but it makes my life easier. It adheres to a standard - but it's certainly not "the" standard.
-
What is the relation between commitizen-tools/commitizen and commitizen/cz-cli?
When I googled, I found cz-cli project first: https://github.com/commitizen/cz-cli
-
Ideas for minimum PHP pipeline for a small team
Same thing with git commits. Something like commitizen. It forces a specific format of your commits. And if you're using an associated issue/bug tracker that can automatically link to commits you can set up to format like that.
-
How do I learn modern web development?
That may also serve as a good entry point for nodeJS via the tools: commitizen, commitLint. That is you implement them within your project, and then also think about how to implement via CI/CD remotely.
standard-version
-
Streamline Your Workflow: Setting Up Git Hooks with Husky to Simplify Version Updates
Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.
-
Starting React Native Project in 2023
We can use standard-version tool to generate a changelog, bump the version of app and create a new tag automatically.
-
Microservices Shared Libraries — Design and Best Practices
There are many great tools to help with automation here, some of them are action-semantic-pull-request to enforce conventional commits and standard version to bump the version and create a changelog according to the conventional commits.
-
Add Commitint, Commitizen, Standard Version, and Husky to SvelteKit Project
I tried gitmoji and followed Make everyone in your project write beautiful commit messages using commitlint and commitizen by @sohandutta, but end up using the setting in this article because it's not compatible to changelog generation of standard-version (Ref: Issue #859)
-
Releasing a pomodoro app #1: programming bit by bit
As a bonus point, the issues you create in your repository can also serve as part of the documentation. You can outline new features there and you will even be able to generate changelogs from the merged pull requests (like I do using conventional-changelog/standard-version).
-
Taiga UI: A year in Open Source
There’s also a husky precommit hook with ESlint and Prettier fixing and formatting changed code on every commit with lint-staged which makes sure malformed code doesn't even make it to the Pull Request. Combined with standard-version and strict commit messages it makes releasing and changelog generation a breeze. For a contributor the workflow is as smooth as:
-
Autodeploy javascript library to npmjs via Github Actions
But you can also automate even more, if, for example, you write according to Conventional Commits, you can also automate the creation of tags using the standard-version library.
-
Automatically generate and release a changelog using Node.js
# Changelog All notable changes to this project will be documented in this file. See \[standard-version\](https://github.com/conventional-changelog/standard-version) for commit guidelines. ## 1.1.0 (2021-07-12) ### Features * **new-feature:** add a new-feature to our project 11c0322
-
Awesome Dev Tools To Automate Code Tasks 🔥
Standard Version
-
versionem - Simple and straightforward automated semantic versioning integrated to changelog generation
So this is like standard-version with less features?
What are some alternatives?
semantic-release - :package::rocket: Fully automated version management and package publishing
tig - Text-mode interface for git
husky - Git hooks made easy 🐶 woof!
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
semver - Semantic Versioning Specification
tortoisegit - Windows Explorer Extension to Operate Git; Mirror of official repository https://tortoisegit.org/sourcecode
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
release-please - generate release PRs based on the conventionalcommits.org spec
towncrier - Manage the release notes for your project.
cz-customizable - A standalone commit message helper or customizable commitizen adapter for https://github.com/commitizen/cz-cli
commitlint - 📓 Lint commit messages