feat: add new feature
# Commit Message Format
# type(scope): subject
#
# Types:
# feat: A new feature
# fix: A bug fix
# docs: Documentation only changes
# style: Changes that do not affect the meaning of the code
# (white-space, formatting, missing semi-colons, etc)
# refactor: A code change that neither fixes a bug nor adds a feature
# perf: A code change that improves performance
# test: Adding missing tests or correcting existing tests
# build: Changes that affect the build system or external dependencies
# ci: Changes to our CI configuration files and scripts
# chore: Other changes that don't modify src or test files
# revert: Reverts a previous commit
#
# Scope:
# The scope could be anything specifying the place of the commit change.
# For example: core, server, integrator, etc.
#
# Subject:
# The subject contains a succinct description of the change.
# Use the imperative, present tense: "change" not "changed" nor "changes"
# Don't capitalize the first letter
# No dot (.) at the end
