feat: Add fish extension
feat: Add fish extension

# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#
# Type
#
# build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
# ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
# docs: Documentation only changes
# feat: A new feature
# fix: A bug fix
# perf: A code change that improves performance
# refactor: A code change that neither fixes a bug nor adds a feature
# style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
# setting: Change tools setting
# test: Adding missing tests or correcting existing tests
#
# Scope
# - ui
# - tool
# - ansible
# - maintenance
#
# Subject
#
# The subject contains succinct description of the change:
#
#     use the imperative, present tense: "change" not "changed" nor "changes"
#     don't capitalize first letter
#     no dot (.) at the end
#
# Body
#
# Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
# Footer
#
# The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
#
# Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.
#
# A detailed explanation can be found in this [document][commit-message-format].

pogin503/dot-files,pogin503/dot-files