chore: reduce noise in files issues and PRs (#9451)

I don't like to always see the boilerplate from the template so I moved it into a summary that can be expanded.
vega · Oct 4, 2024 · d3ec513 · d3ec513
1 parent a1a2693
commit d3ec513
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 3 deletions.
diff --git a/.github/ISSUE_TEMPLATE/Bug_report.md b/.github/ISSUE_TEMPLATE/Bug_report.md
@@ -6,6 +6,7 @@ labels: 'Bug :bug:'
 
 ## Bug Description
 
+<!--
 Describe how to reproduce this bug. Provide an [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) spec in JSON, wrapped by triple backticks like this:
 
 ```json
@@ -16,7 +17,10 @@ Describe how to reproduce this bug. Provide an [minimal, reproducible example](h
 ```
 
 If applicable, include error messages and screenshots, videos, or working examples (e.g. by clicking share in the [Vega-Editor](https://vega.github.io/editor/).
+-->
 
-## Checklist
+<details>
+  <summary><h2>Checklist</h2></summary>
 
 - [ ] I checked for duplicate issues.
+</details>
diff --git a/.github/ISSUE_TEMPLATE/Enhancement.md b/.github/ISSUE_TEMPLATE/Enhancement.md
@@ -6,6 +6,7 @@ labels: 'Enhancement :tada:'
 
 ## Enhancement Description
 
+<!--
 Describe the feature's goal, motivating use cases, and its expected behavior.
 
 If you are proposing a new syntax, please provide at least one example spec, wrapped by triple backticks like this:
@@ -18,7 +19,10 @@ If you are proposing a new syntax, please provide at least one example spec, wra
 ```
 
 You are encouraged to prototype multiple alternative syntaxes for your proposed feature. Doing so often leads to a better design.
+-->
 
-## Checklist
+<details>
+  <summary><h2>Checklist</h2></summary>
 
 - [ ] I checked for duplicate issues.
+</details>
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,7 @@
 ## PR Description
 
-## Checklist
+<details>
+  <summary><h2>Checklist</h2></summary>
 
 - [ ] This PR is atomic (i.e., it fixes one issue at a time).
 - [ ] The title is a concise [semantic commit message](https://www.conventionalcommits.org/) (e.g. "fix: correctly handle undefined properties").
@@ -13,3 +14,4 @@ Tips:
 
 - https://medium.com/@greenberg/writing-pull-requests-your-coworkers-might-enjoy-reading-9d0307e93da3 is a nice article about writing a nice PR.
 - Use draft PR for work in progress PRs / when you want early feedback (https://github.blog/2019-02-14-introducing-draft-pull-requests/).
+</details>