# Commit Message Template # ▼ Write

# ▼ # ▼ Write # ▼ # ▼ Write

# Explanation of Format # - General Commit #

# - Required # - Format: (): # # - Required # - build: Changes affecting the build system or external dependencies (e.g., gulp, broccoli, npm) # - ci: Changes to CI configuration files or scripts (e.g., CircleCi, SauceLabs) # - config: Add or update configuration files # - docs: Documentation updates # - feat: Adding new features # - fix: Bug fixes # - perf: Changes that improve performance # - refactor: Changes that are neither adding a feature nor fixing a bug # - remove: Code or file removals # - style: Changes related to styling or formatting # - test: Adding or updating tests # # - Optional # - Name of the npm package or the part of the code affected by the change # - Examples: location, browser, compile, rootScope... # # - Required # - Concisely describe the change # - Use lowercase for the first letter, present tense, imperative mood, and do not end with a period. # # # - At least 20 characters required (except for docs) # - Write in present tense, imperative mood # - Explain the motivation (why) behind the changes # - May include a comparison of the previous behavior and the new behavior to clarify the impact # #

# - Include Breaking Changes, deprecations, or references to related GitHub issues, Jira tickets, or pull requests # - Examples: # - 1. Breaking Changes # BREAKING CHANGE:

# # # # # Fixes # # - 2. Deprecations # DEPRECATED: # # # # # Closes # # # - Revert Commit #

# revert:

# # - This reverts commit # - Provide a clear explanation for the revert