git-commitizen
| Crates.io | git-commitizen |
| lib.rs | git-commitizen |
| version | 0.1.1 |
| source | src |
| created_at | 2024-08-28 07:09:51.935962 |
| updated_at | 2024-09-25 09:26:56.019076 |
| description | A simple commitizen CLI tool in rust |
| homepage | https://github.com/k3ii/git-cz |
| repository | https://github.com/k3ii/git-cz |
| max_upload_size | |
| id | 1354293 |
| size | 690,284 |
Jain Ramchurn (k3ii)
documentation
README
git-cz
git-cz is a simple commitizen tool written in rust.
git-cz helps you create conventional commits with ease.
It prompts you to select the type of commit, enter a scope (optional), and provide a summary and detailed description.
Features
-
Prompts for commit type, scope, summary, and detailed description.
Installation
cargo install git-commitizen
[!NOTE] Although the package is called
git-commitizenon crates.io, the installed binary is namedgit-cz:
Check releases for pre-built binaries or compiled binary for your platform.
Conventional Commits
The Conventional Commits specification is a convention for writing consistent commit messages. It helps in automating the release process, generating changelogs, and making it easier to understand the history of a project.
Format
A conventional commit message has the following format:
<type>(<scope>): <summary>
<body>
<footer>
type: The type of change being committed, e.g., feat, fix, docs, etc.scope(optional): The part of the codebase that is being affected.summary: A brief summary of the change.body(optional): A detailed description of the change.footer(optional): A footer section that can contain additional information about issues fixed or closed.
Benefits
- Automated Changelog: By following a consistent commit message format, tools can automatically generate changelogs.
- Better Collaboration: It makes it easier for teams to understand the nature of changes in the codebase.
- Semantic Versioning: Helps in determining the version of the project automatically based on the types of commits.
How Git Picks Up git-cz
Git has a feature called "Git command aliases" that allows it to treat any executable file named git-<command> in your PATH as a Git subcommand. This is how git-cz works:
- When you run
git cz, Git looks for an executable file namedgit-czin the directories listed in your PATH. - If it finds such a file (which is our script), Git executes it as if it were a built-in Git command.
- This mechanism allows you to create custom Git commands without modifying Git itself.
By naming our script git-cz and placing it in a directory in the PATH, we're effectively creating a new Git command cz that can be invoked as git cz.
This approach is flexible and allows for easy installation and use across different projects without requiring project-specific configuration.
See also
Contributing
Feel free to improve the script to add your own commit types or make any other enhancements you think are useful. Contributions are welcome!
If you would like to contribute:
- Fork the repository.
- Create a new branch for your feature or fix.
- Make your changes.
- Submit a pull request.
Your contributions can help make this tool even more useful for everyone. Thank you for considering contributing!