From 62e8a7fb016b68975ea4dcc2eccdd2b6e1a4e671 Mon Sep 17 00:00:00 2001
From: Jarred Sumner <jarred@jarredsumner.com>
Date: Mon, 28 Jul 2025 15:44:53 -0700
Subject: [PATCH] Update pull_request_template.md

---
 .github/pull_request_template.md | 47 --------------------------------
 1 file changed, 47 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index f8cfaaff8d..b4369fa1a4 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,50 +1,3 @@
 ### What does this PR do?
 
-<!-- **Please explain what your changes do**, example: -->
-
-<!--
-
-This adds a new flag --bail to bun test. When set, it will stop running tests after the first failure. This is useful for CI environments where you want to fail fast.
-
--->
-
-- [ ] Documentation or TypeScript types (it's okay to leave the rest blank in this case)
-- [ ] Code changes
-
 ### How did you verify your code works?
-
-<!-- **For code changes, please include automated tests**. Feel free to uncomment the line below -->
-
-<!-- I wrote automated tests -->
-
-<!-- If JavaScript/TypeScript modules or builtins changed:
-
-- [ ] I included a test for the new code, or existing tests cover it
-- [ ] I ran my tests locally and they pass (`bun-debug test test-file-name.test`)
-
--->
-
-<!-- If Zig files changed:
-
-- [ ] I checked the lifetime of memory allocated to verify it's (1) freed and (2) only freed when it should be
-- [ ] I included a test for the new code, or an existing test covers it
-- [ ] JSValue used outside of the stack is either wrapped in a JSC.Strong or is JSValueProtect'ed
-- [ ] I wrote TypeScript/JavaScript tests and they pass locally (`bun-debug test test-file-name.test`)
--->
-
-<!-- If new methods, getters, or setters were added to a publicly exposed class:
-
-- [ ] I added TypeScript types for the new methods, getters, or setters
--->
-
-<!-- If dependencies in tests changed:
-
-- [ ] I made sure that specific versions of dependencies are used instead of ranged or tagged versions
--->
-
-<!-- If a new builtin ESM/CJS module was added:
-
-- [ ] I updated Aliases in `module_loader.zig` to include the new module
-- [ ] I added a test that imports the module
-- [ ] I added a test that require() the module
--->