Skip to content

Commit

Permalink
GH: use an issue form for bug reports
Browse files Browse the repository at this point in the history
Lots of bug reports currently just omit information which we'd like
to have. Usually this means we have to ask follow up question.

Let's try using an issue form in the hopes of getting more complete
answers.

Signed-off-by: Lorenz Bauer <lmb@isovalent.com>
  • Loading branch information
lmb authored and ti-mo committed Dec 14, 2023
1 parent 495817d commit 8ebad5c
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 23 deletions.
23 changes: 0 additions & 23 deletions .github/ISSUE_TEMPLATE/bug_report.md

This file was deleted.

36 changes: 36 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
name: Bug report
description: Create a report to help us improve
labels: ["bug"]
assignees: []

body:
- type: markdown
attributes:
value: "Thank you for reporting a bug. Please fill out the fields below."

- type: textarea
attributes:
label: Describe the bug
description: |
A clear and concise description of what the bug is.
Include what you expected to happen instead.
render: markdown
validations:
required: true

- type: textarea
attributes:
label: How to reproduce
description: "Steps to reproduce the behavior."
render: shell
validations:
required: true

- type: input
id: version
attributes:
label: Version information
description: The output of `go list -m github.com/cilium/ebpf`.
placeholder: github.com/cilium/ebpf vX.Y.Z
validations:
required: true

0 comments on commit 8ebad5c

Please sign in to comment.