These are common commit message prefixes or types that can be used to indicate the purpose of a commit in a project's version control history. Here's what each of them typically means:
✓ build: Changes related to the build system or external dependencies, such as package updates, build tool configuration changes, or CI/CD pipeline updates.
✓ chore: Changes that do not affect the code, such as updating documentation, refactoring code comments, or making minor code changes that don't affect the functionality of the application.
✓ ci: Changes to the continuous integration (CI) configuration files or scripts.
✓ docs: Changes to documentation files, such as user guides, README files, or API documentation.
✓ feat: The addition of a new feature to the application or library.
✓ fix: The resolution of a bug or issue in the application or library.
✓ perf: Changes related to performance optimization, such as code refactoring to improve execution speed or reduce memory usage.
✓ refactor: Changes to the codebase that do not add new features or fix bugs, but improve the overall structure or readability of the code.
✓ revert: A commit that undoes a previous commit.
✓ style: Changes to the code that do not affect its functionality, but improve its readability or aesthetics, such as code formatting, indentation, or naming conventions.
✓ test: Changes or additions to automated tests, such as unit tests, integration tests, or end-to-end tests.
These commit message prefixes can help to provide context and organization in a project's version control history, making it easier to understand and track changes over time.
Note: if you want to force these rules on commit messages, here is a commit linting lib for you. Commitlint
Top comments (0)