Skip to content

Commit dd19f80

Browse files
committed
chore: add repro instructions
1 parent dc3743a commit dd19f80

File tree

2 files changed

+13
-3
lines changed

2 files changed

+13
-3
lines changed

.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ body:
2828
- type: markdown
2929
attributes:
3030
value: |
31-
Check out PLACEHOLDER for advice on producing a reproduction repo.
31+
Check out [our contributing guide](https://github.com/netlify/next-runtime/blob/main/CONTRIBUTING.md#how-to-make-a-minimal-reproduction) for advice on producing a reproduction repo.
3232
- type: textarea
3333
attributes:
3434
label: Expected Result

CONTRIBUTING.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,5 +45,15 @@ Most common commit message prefixes are:
4545

4646
## Releasing
4747

48-
1. Merge the release PR
49-
2. Run `npm publish`
48+
This repository uses [release-please](https://github.com/googleapis/release-please) to automate its releases.
49+
50+
## How to make a minimal reproduction
51+
52+
A reproducible test case is a small Next.js site built to demonstrate a problem - often this problem is caused by a bug in Next.js, next-runtime or user code. Your reproducible test case should contain the bare minimum features needed to clearly demonstrate the bug.
53+
54+
Steps to create a reproducible test case:
55+
56+
- Create a new Next.js site: `npx create-next-app@latest`
57+
- Add any code or functionality related to the issue. For example, if you have problems with middleware functionality you should add all the necessary code of your middleware.
58+
- Verify that you're seeing the expected error(s) when running `netlify serve` and on a deployed version on [Netlify](https://www.netlify.com)
59+
- Publish the code (your GitHub account is a good place to do this) and then link to it when creating an issue. While creating the issue, please give as many details as possible. This could also include screenshots of error messages.

0 commit comments

Comments
 (0)