When contributing to any project, use the following keywords in your commit messages to clearly indicate the type of change being made:
feat: Introduces a new feature. Example:feat: Add user authenticationfix: Addresses a bug or issue. Example:fix: Resolve issue with broken link on homepagestyle: Changes the code style or formatting (no functional changes). Example:style: Enforce consistent indentation across codebaserefactor: Improves code structure or organization without adding features or fixing bugs. Example:refactor: Extract database connection logic into separate moduleadd: Creates a new capability (feature, test, dependency, etc.). Example:add: Implement unit tests for data validationdrop: Removes a capability (feature, test, dependency, etc.). Example:drop: Remove unused analytics librarybump: Increases the version of a dependency or tool. Example:bump: Upgrade React version to 18.2make: Changes to the build process, tools, or infrastructure. Example:make: Update webpack configuration for production buildsstart: Begins a process or enables a feature (e.g., a toggle or feature flag). Example:start: Enable new payment processing systemstop: Ends a process or disables a feature (e.g., a toggle or feature flag). Example:stop: Disable deprecated API endpointoptimize: A performance-focused change that improves speed or efficiency. Example:optimize: Improve query performance for user profilesdocumentordocs: Changes related solely to documentation. Example:docs: Update API documentation for new endpointchore: General maintenance tasks, dependency upgrades, etc. Example:chore: Update dependencies to latest versionstest: Changes related to adding or correcting tests. Example:test: Add integration tests for payment processing
Linking to Issues/Work Items:
If your commit relates to a specific issue or work item in the tracking system, include the issue ID in the commit message (e.g., fix: Resolve issue #123 - User profile update error).