Skip to content

Commit f8ad36e

Browse files
committed
issue templates
1 parent ce4b9ab commit f8ad36e

4 files changed

Lines changed: 105 additions & 128 deletions

File tree

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 0 additions & 32 deletions
This file was deleted.

.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 71 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,91 @@
1-
name: 🐛 Report an Issue
2-
description: File a bug report to help improve Pipelex
3-
title: "bug: "
4-
labels: ["bug-unverified"]
1+
name: "🐞 Bug report"
2+
description: "Report a reproducible problem with the library"
3+
type: Bug
4+
labels:
5+
- status:needs-triage
6+
57
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
**Thanks for taking the time to file a bug!**
12+
Please complete **all required sections**—incomplete reports will be sent back for more information.
13+
14+
- type: checkboxes
15+
id: confirmations
16+
attributes:
17+
label: "Before submitting"
18+
options:
19+
- label: "I'm using the **latest released** version of the library"
20+
required: true
21+
- label: "I've searched [open issues](issues?q=is%3Aissue%20state%3Aopen%20type%3ABug) and found no duplicate"
22+
required: true
23+
624
- type: textarea
25+
id: description
726
attributes:
8-
label: Issue Description
9-
description: Provide a clear and detailed description of the issue you encountered and what you expected to happen instead.
10-
placeholder: |
11-
What happened?
12-
What did you expect to happen?
27+
label: "Describe the bug, tell us what went wrong"
28+
placeholder: "A clear and concise description of what went wrong. What did you expect to happen vs. what actually happened."
1329
validations:
1430
required: true
1531

1632
- type: textarea
33+
id: reproduction
1734
attributes:
18-
label: Reproduction Steps
19-
description: Help us understand the issue by providing detailed steps to reproduce it. Include code examples, error messages, or configuration files if relevant.
35+
label: "Reproduction snippet"
36+
description: "How can we reproduce the bug?"
2037
placeholder: |
21-
1. Install package with '...'
22-
2. Configure pipeline with '...'
23-
3. Run the following code '...'
24-
4. Error occurs
38+
Provide the cli command that reproduces the bug:
39+
```bash
40+
# paste command here
41+
```
42+
or the smallest possible script that reproduces the bug:
43+
```python
44+
# paste code here
45+
```
46+
validations:
47+
required: false
48+
49+
- type: input
50+
id: lib_version
51+
attributes:
52+
label: "Library version"
53+
placeholder: "e.g. 1.4.2"
2554
validations:
2655
required: true
2756

57+
- type: input
58+
id: python_version
59+
attributes:
60+
label: "Python version"
61+
placeholder: "e.g. 3.12.0"
62+
validations:
63+
required: true
64+
65+
- type: input
66+
id: os
67+
attributes:
68+
label: "Operating system"
69+
placeholder: "e.g. Ubuntu 22.04 LTS / MacOS 14.3"
70+
validations:
71+
required: false
72+
2873
- type: textarea
74+
id: logs
2975
attributes:
30-
label: Environment Details
31-
description: Please provide information about your setup. This helps us identify if the issue is environment-specific.
32-
placeholder: |
33-
- Python Version:
34-
- Pipelex Version:
35-
- Operating System:
36-
- Installation Method (pip/poetry/uv):
37-
- Relevant Dependencies:
76+
label: "Stack trace / error output"
77+
description: "Paste any relevant logs here."
78+
render: shell
79+
validations:
80+
required: false
3881

3982
- type: textarea
83+
id: extra
4084
attributes:
41-
label: Additional Context
42-
description: Add any other relevant information, screenshots, logs, or context that might help us understand and fix the issue.
43-
placeholder: |
44-
Error logs, related configuration, or other helpful details...
85+
label: "Additional context & screenshots"
86+
placeholder: "Anything else that might help us debug."
87+
validations:
88+
required: false
4589

4690
- type: dropdown
4791
id: contribution
@@ -53,13 +97,3 @@ body:
5397
- "Yes, I'd like to contribute"
5498
validations:
5599
required: true
56-
57-
- type: checkboxes
58-
attributes:
59-
label: Confirmations
60-
description: Please confirm the following
61-
options:
62-
- label: I have checked that this issue hasn't already been reported
63-
required: true
64-
- label: I have tested with the latest version of Pipelex
65-
required: true

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 0 additions & 19 deletions
This file was deleted.
Lines changed: 34 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,62 +1,56 @@
1-
name: 💡 Feature Request
2-
description: Suggest a new feature or improvement
3-
title: "feat: "
4-
labels: ["enhancement"]
1+
name: "✨ Feature request"
2+
description: "Suggest an idea or improvement for the library"
3+
type: Feature
4+
labels:
5+
- status:needs-triage
6+
57
body:
6-
- type: textarea
8+
- type: markdown
79
attributes:
8-
label: Problem Statement
9-
description: Describe the problem you're trying to solve or the limitation you're facing.
10-
placeholder: |
11-
What's the challenge you're encountering?
12-
Why is this important to address?
13-
validations:
14-
required: true
10+
value: |
11+
**Thanks for contributing an idea!**
12+
Please fill in the sections below so we can understand and prioritise your request.
13+
14+
- type: checkboxes
15+
id: confirmations
16+
attributes:
17+
label: "Before submitting"
18+
options:
19+
- label: "I've searched [open issues](issues?q=is%3Aissue%20state%3Aopen%20type%3AFeature) and found no similar request"
20+
required: true
21+
- label: "I'm willing to start a discussion or contribute code"
22+
required: false
1523

1624
- type: textarea
25+
id: problem
1726
attributes:
18-
label: Proposed Solution
19-
description: Describe your ideal solution to the problem. Be as specific as possible.
20-
placeholder: |
21-
How would you like this to work?
22-
What would the user experience be like?
27+
label: "Problem / motivation"
28+
placeholder: "What problem does this feature solve? Who is affected and why?"
2329
validations:
2430
required: true
2531

2632
- type: textarea
33+
id: proposal
2734
attributes:
28-
label: Alternative Approaches
29-
description: Describe any alternative solutions or features you've considered.
30-
placeholder: |
31-
What other ways might this problem be solved?
32-
What are the trade-offs of different approaches?
35+
label: "Proposed solution"
36+
placeholder: "Describe the feature you’d like to see."
37+
validations:
38+
required: false
3339

3440
- type: textarea
41+
id: alternatives
3542
attributes:
36-
label: Implementation Ideas
37-
description: If you have any thoughts on how this could be implemented, share them here.
38-
placeholder: |
39-
Technical considerations
40-
Potential challenges
41-
Integration points
43+
label: "Alternatives considered"
44+
placeholder: "Any work-arounds you’ve tried or other approaches you considered."
45+
validations:
46+
required: false
4247

4348
- type: dropdown
4449
id: contribution
4550
attributes:
4651
label: Would you like to help implement this feature?
47-
description: We welcome contributions and can provide guidance!
4852
options:
4953
- "Not at this time"
5054
- "Yes, I'd like to contribute"
5155
validations:
52-
required: true
53-
54-
- type: checkboxes
55-
attributes:
56-
label: Confirmations
57-
description: Please confirm the following
58-
options:
59-
- label: I have searched for similar feature requests
60-
required: true
61-
- label: This feature would benefit the broader community
62-
required: true
56+
required: false

0 commit comments

Comments
 (0)