# <type>(<scope>): <subject>

# Explain why this change is being made
# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|

# Provide links or keys to any relevant tickets, articles or other resources
# Example: Fixes #23

# --- COMMIT END ---
# Type can be:
#    feat     (new feature)
#    fix      (bug fix)
#    refactor (refactoring code)
#    style    (formatting, etc; no code change)
#    docs     (changes to documentation)
#    test     (adding or refactoring tests; no production code change)
#    chore    (updating build tasks etc; no production code change)
#    perf     (performance improvement)
#    ci       (CI/CD changes)
#    build    (build system changes)
#    revert   (revert a previous commit)
# --------------------
# Scope can be:
#    conv       (changes to conv package)
#    entry      (changes to entry package)
#    parser     (changes to parser package)
#    proc       (changes to processor package)
#    vis        (changes to vis package)
#    deps       (dependency updates)
#    ci         (CI/CD changes)
#    docs       (documentation)
# --------------------
# Remember to:
#    - Use imperative mood in subject line
#    - Do not end the subject line with a period
#    - Separate subject from body with a blank line
#    - Use the body to explain what and why vs. how
#    - Use multiple lines with "-" for bullet points in body
#    - Use BREAKING CHANGE: in footer for breaking changes
# --------------------
