# Git Commit Message Template with Issue ID and Conventional Commits

# ================================================================
#
# This template requires the commit header to begin with an Issue ID.
#
# Format: <issue-id> <type>(<scope>): <subject>
#
# - <issue-id>: The identifier for the related issue (e.g., "ISSUE-123").
#               This comes first per your team's convention.
#
# - <type>: Describes the kind of change. Common types include:
#     feat     - A new feature
#     fix      - A bug fix
#     docs     - Documentation changes
#     style    - Code style changes (formatting, etc.)
#     refactor - Code refactoring that neither adds features nor fixes bugs
#     perf     - Performance improvements
#     test     - Adding or updating tests
#     chore    - Build process or auxiliary tool changes
#
# - <scope>: (Optional) A noun describing the section of the codebase affected.
#            Examples: auth, api, ui, config.
#
# - <subject>: A short, imperative tense description of the change.
#
# Example:
#   ISSUE-123 feat(auth): add OAuth login support
#
# ---------------------------------------------------
# 2. BODY (Optional):
# ---------------------------------------------------
# Provide a detailed explanation of the commit:
# - Describe the what and why of the changes.
# - Use 72-character line wraps.
#
# ---------------------------------------------------
# 3. FOOTER (Optional):
# ---------------------------------------------------
# Include any metadata such as:
# - Issue references (e.g., Fixes #456)
# - Breaking changes (prefixed with "BREAKING CHANGE:")
#
# Example:
#   BREAKING CHANGE: The authentication API now requires an OAuth token.
#
# IMPORTANT:
# Remove these instructional comments before finalizing your commit.
#
# ----------------------------
# START WRITING YOUR COMMIT MESSAGE BELOW:
# ----------------------------

docs: Update README.md to contain Open Knight Tour

Author: Kalkwst

README.md

@@ -246,6 +246,8 @@ find more than one implementation for the same objective but using different alg
       * [Proposer](./Algorithms/Problems/StableMarriage/Proposer.cs)
     * [N-Queens](./Algorithms/Problems/NQueens)
       * [Backtracking](./Algorithms/Problems/NQueens/BacktrackingNQueensSolver.cs)
+    * [Knight Tour](./Algorithms/Problems/KnightTour/)
+      * [Open Knight Tour](./Algorithms/Problems/KnightTour/OpenKnightTour.cs)
     * [Dynamic Programming](./Algorithms/Problems/DynamicProgramming)
       * [Coin Change](./Algorithms/Problems/DynamicProgramming/CoinChange/DynamicCoinChangeSolver.cs)
       * [Levenshtein Distance](./Algorithms/Problems/DynamicProgramming/LevenshteinDistance/LevenshteinDistance.cs)