Commit Message Convention

Each commit message must follow one of the two formats below:

Additional details about the commit sections:

Prefix: The commit message should always begin with an action verb in its infinitive form. The verb should describe the type of change being made.
Description: After the verb, provide a brief description of what has been done in that commit. Avoid past tense or gerunds (form of a verb that ends in "-ing" and functions as a noun in a sentence).
Body (Optional): There are no specific rules for the commit body. You can add details as necessary in subsequent lines.

Examples

Verb	Description	Example
ADD	Introduces new functionality, features, or files	`[ADD] cron jobs to clean expired tokens`
FIX	Corrects bugs or issues in the codebase	`[FIX] the database connection timeout`
UPDATE	Improves or modifies existing functionality	`[UPDATE] the login flow for better UX`
REMOVE	Deletes or removes code, files, or dependencies	`[REMOVE] outdated npm packages`
EDIT	Adjusts or alters existing code without major change	`[EDIT] the README for better clarity`
REFACTOR	Refactors code without changing its behavior	`[REFACTOR] server-side validation logic`
RENAME	Renames files or variables	`[RENAME] variables to follow naming convention`
MERGE	Merges branches or pull requests	‘[MERGE] branch 'feature-auth’ into dev`

Prefixes should always be in uppercase to clearly identify the action if they are encapsulated by [], however, if they are followed not encapsulated by [] and followed by a : they should be in lowercase.
Try to keep descriptions concise and to the point. Use the body for further elaboration if needed.
If the commit is related to workflows or external dependencies, be explicit in the description.