From f89b852aa26ce3733c55f1bf08e47b22e4ec99ef Mon Sep 17 00:00:00 2001
From: Thomas Mauran <78204354+thomas-mauran@users.noreply.github.com>
Date: Tue, 19 Nov 2024 19:34:27 +0100
Subject: [PATCH] chore: create refactor template md

---
 .github/ISSUE_TEMPLATE/refactor_request.md | 49 ++++++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/refactor_request.md

diff --git a/.github/ISSUE_TEMPLATE/refactor_request.md b/.github/ISSUE_TEMPLATE/refactor_request.md
new file mode 100644
index 0000000..b55cb7d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/refactor_request.md
@@ -0,0 +1,49 @@
+---
+name: Refactor request
+about: Propose improvements to the code structure or architecture
+title: ""
+labels: refactor
+assignees: ""
+
+---
+
+### Problem
+
+<!-- 
+Describe the current issue with the codebase or specific part of the code that you believe need refactoring.
+-->
+
+---
+
+### Proposed Refactor Plan
+
+<!-- 
+Provide a detailed plan for refactoring.
+Consider including:
+- Suggestions for breaking down large files (e.g., separating `board.rs` into smaller modules)
+- Improving code structure or reducing duplication
+- Enhancing testability or modularity of the codebase
+- Potentially introducing design patterns or Rust best practices
+-->
+
+---
+
+### Expected Benefits
+
+<!-- 
+Outline the benefits of the proposed refactor.
+Examples:
+- Easier maintainability and readability of the code
+- Improved test coverage and debugging experience
+- Better performance or reduced technical debt
+-->
+
+---
+
+### Additional Context
+
+<!-- 
+Add any other context, such as:
+- Relevant files or code snippets needing attention
+- Links to documentation, tools, or examples to support your suggestion
+-->