From 010d3413b02cbfde24d94b1275e0d0d0566c20da Mon Sep 17 00:00:00 2001
From: Justus Adam <dev@justus.science>
Date: Thu, 14 Sep 2023 13:42:12 -0700
Subject: [PATCH] Make the PR template descriptions not comments (#35)

## What Changed?

This removes the comment tags from the PR template.

## Why Does It Need To?

This is to encourage the submitter of the PR to overwrite the
description so it won't show up in the final, squashed commit message.

## Checklist

- [x] Above description has been filled out so that upon quash merge we
have a
  good record of what changed.
- [x] New functions, methods, types are documented. Old documentation is
updated
  if necessary
- [x] Documentation in Notion has been updated
- [x] Tests for new behaviors are provided
  - [x] New test suites (if any) ave been added to the CI tests (in
`.github/workflows/rust.yml`) either as compiler test or integration
test.
*Or* justification for their omission from CI has been provided in this
PR
    description.
---
 .github/pull_request_template.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index a06e803a60..e6269cc012 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,12 +1,9 @@
 ## What Changed?
 
-<!-- 
 A summary of what you are proposing to change.
--->
 
 ## Why Does It Need To?
 
-<!-- 
 Describe the concern this change addresses. 
 
 Reference any issues that are related and use closing words such as "fixes" or
@@ -16,7 +13,6 @@ You can find out more about closing words here:
 https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests
 
 Try to make your PR about one single concern or issue, unless they are mutually dependent.
--->
 
 ## Checklist