Skip to content

Commit 14b1337

Browse files
Update issue templates
1 parent fadf442 commit 14b1337

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

.github/ISSUE_TEMPLATE/bug-report.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
name: Bug report
3+
about: Report a Tailwind CSS issue.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
<!-- Please provide all of the information requested below. We're a small team and without all of this information it's not possible for us to help and your bug report will be closed. -->
11+
12+
**What version of Tailwind CSS are you using?**
13+
14+
For example: v4.0.6
15+
16+
**What build tool (or framework if it abstracts the build tool) are you using?**
17+
18+
For example: postcss-cli 11.0.0, Next.js 15.1.7, Vite 6.1.0
19+
20+
**What version of Node.js are you using?**
21+
22+
For example: v20.0.0
23+
24+
**What browser are you using?**
25+
26+
For example: Chrome, Safari, or N/A
27+
28+
**What operating system are you using?**
29+
30+
For example: macOS, Windows
31+
32+
**Reproduction URL**
33+
34+
A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. **Please do not link to your actual project**, what we need instead is a _minimal_ reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.
35+
36+
A reproduction is **required** when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.
37+
38+
**Describe your issue**
39+
40+
Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.

0 commit comments

Comments
 (0)