From a14bdf619c1a57f9617947e90037ce8c59de6279 Mon Sep 17 00:00:00 2001
From: qwerty287 <80460567+qwerty287@users.noreply.github.com>
Date: Mon, 26 Aug 2024 08:29:08 +0200
Subject: [PATCH] Use MD PR template (#4057)

---
 ...request_template.txt => pull_request_template.md} | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)
 rename .github/{pull_request_template.txt => pull_request_template.md} (83%)

diff --git a/.github/pull_request_template.txt b/.github/pull_request_template.md
similarity index 83%
rename from .github/pull_request_template.txt
rename to .github/pull_request_template.md
index ec43d6ff4..46dd8d027 100644
--- a/.github/pull_request_template.txt
+++ b/.github/pull_request_template.md
@@ -1,15 +1,11 @@
+<!--
+
 Please check the following tips:
-
 1. Avoid using force-push and commands that require it (such as `commit --amend` and `rebase origin/main`). This makes it more difficult for the maintainers to review your work. Add new commits on top of the current branch, and merge the new state of `main` into your branch with plain `merge`.
-
 2. Provide a meaningful title for this pull request. It will be used as the commit message when this pull request is merged. Add as many commits as you like with any messages you like, they will be squashed into one commit.
-
-3. If this pull request fixes an issue, refer to the issue with messages like `Ref #1234`, `Closes #1234`, or `Fixes #1234` in the pull description.
-
+3. If this pull request fixes an issue, refer to the issue with messages like `Closes #1234`, or `Fixes #1234` in the pull description.
 4. Please check that you are targeting the `main` branch. Pull requests on release branches are only allowed for backports.
-
 5. Make sure you have read contribution guidelines: https://woodpecker-ci.org/docs/development/getting-started
-
 6. It is recommended to enable "Allow edits by maintainers", so maintainers can help you more easily.
 
-Make sure to remove these tips (or replace them with a description) after you have read them.
+-->