cz-cli
cz-customizable
cz-cli | cz-customizable | |
---|---|---|
31 | 2 | |
16,435 | 583 | |
0.9% | 0.9% | |
2.3 | 0.0 | |
about 2 months ago | 3 months 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.
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.
cz-customizable
-
Make everyone in your project write beautiful commit messages using commitlint and commitizen π
Coming to the last part, now we will create a CLI helper to generate the commit message using commitizen. Also we are using cz-customizable to customize the CLI helper.
-
Let's make your own commit message template with cz-format-extension
cz-customizable is great library. However that provides a few option. This point is what I started create cz-format-extension. cz-format-extension has high expandable, and also dependencies keeps latest.
What are some alternatives?
semantic-release - :package::rocket: Fully automated version management and package publishing
gitmoji - An emoji guide for your commit messages. π
tig - Text-mode interface for git
gitmoji-commit-workflow - π Gitmoji Commit Workflow
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
cz-format-extension - Extension for commitizen format
tortoisegit - Windows Explorer Extension to Operate Git; Mirror of official repository https://tortoisegit.org/sourcecode
git-repo-info
release-please - generate release PRs based on the conventionalcommits.org spec
git-js - A light weight interface for running git commands in any node.js application.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
commitlint - π Lint commit messages