From ee11e48f613768f968e6f0f42a1571a2eaca50c7 Mon Sep 17 00:00:00 2001 From: theEvilReaper Date: Mon, 21 Oct 2024 19:18:36 +0200 Subject: [PATCH] Fix double or usage --- .github/pull_request_template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 6091b70..424b780 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -26,7 +26,7 @@ SOFTWARE. When creating a pull request, it is essential to provide a clear and concise description of the changes being proposed. This description serves as a communication tool to inform the maintainers about the intended modifications. If the pull -request addresses a bug or or implements a feature request, it is important to link to the corresponding issue for context. +request addresses a bug or implements a feature request, it is important to link to the corresponding issue for context. Additionally, the description should outline the rationale behind the changes, any relevant implementation details, and potential impacts on existing functionality. By including this information, you facilitate a smoother review process and help maintainers understand the significance of the proposed changes.