meta: clarify recommendation for bug reproductions

Sometimes reporters link to a repo for their repro, which not only likely takes them more time to setup, but also is less convenient for maintainers. Setting up a repo goes against the idea of a minimal repro, as if it was actually minimal, they would not have bothered creating a repo. PR-URL: #50882 Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ruy Adorno <[email protected]>

Author: aduh95

.github/ISSUE_TEMPLATE/1-bug-report.yml

@@ -27,7 +27,11 @@ body:
  - type: textarea
 attributes:
 label: What steps will reproduce the bug?
-description: Enter details about your bug, preferably a simple code snippet that can be run using `node` directly without installing third-party dependencies.
+description: >
+ Enter details about your bug, preferably a simple code snippet that can
+ be run using `node` directly without installing third-party dependencies
+ or downloading code from the internet (i.e. no ZIP archive, no GitHub
+ repository, etc.).
  - type: textarea
 attributes:
 label: How often does it reproduce? Is there a required condition?