Files
runc/.github/ISSUE_TEMPLATE/bug_report.yaml
T
Rodrigo Campos f55400dce8 .github: Improve issue template description
We received several times issues that the repro steps are human readable
text with ambiguous instructions. That usually ends up in maintainers
asking questions so people provide clear steps.

Let's just make the issue template more clear in that regard.

Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
2025-03-24 12:22:07 +01:00

57 lines
1.7 KiB
YAML

# Forked from https://github.com/containerd/nerdctl/blob/v1.2.1/.github/ISSUE_TEMPLATE/bug_report.yaml
name: Bug report
description: Create a bug report to help improve runc
labels: kind/unconfirmed-bug-claim
body:
- type: markdown
attributes:
value: |
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
When reporting a security issue, do not create an issue or file a pull request on GitHub.
See [`opencontainers/.github/SECURITY.md`](https://github.com/opencontainers/.github/blob/master/SECURITY.md).
- type: textarea
attributes:
label: Description
description: |
Briefly describe the problem you are having in a few paragraphs.
validations:
required: true
- type: textarea
attributes:
label: Steps to reproduce the issue
description: |
As much as possible, try to make steps that would work in a script. This makes the repro unambiguous and easy to follow.
value: |
1.
2.
3.
- type: textarea
attributes:
label: Describe the results you received and expected
validations:
required: true
- type: textarea
attributes:
label: What version of runc are you using?
placeholder: runc --version
validations:
required: true
- type: textarea
attributes:
label: Host OS information
placeholder: cat /etc/os-release
- type: textarea
attributes:
label: Host kernel information
placeholder: uname -a