forgejo-runner

 1name: 🐛 Bug Report
 2description: Found something you weren't expecting? Report it here!
 3title: "bug: "
 4labels: ["Kind/Bug"]
 5body:
 6  - type: markdown
 7    attributes:
 8      value: |
 9        **NOTE: If your issue is a security concern, please email <security@forgejo.org> (GPG: `A4676E79`) instead of opening a public issue.**
10  - type: markdown
11    attributes:
12      value: |
13        - Please speak English, as this is the language all maintainers can speak and write.
14        - Be as clear and concise as possible. A very verbose report is harder to interpret in a concrete way.
15        - Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
16        - Take a moment to [check that your issue hasn't been reported before](https://code.forgejo.org/forgejo/runner/issues?q=&type=all&labels=19).
17  - type: dropdown
18    id: can-reproduce
19    attributes:
20      label: Can you reproduce the bug on the Forgejo test instance?
21      description: |
22        Please try reproducing your issue at https://dev.next.forgejo.org.
23        It is running the latest development branch and will confirm the problem is not already fixed.
24        If you can reproduce it, provide a URL in the description.
25      options:
26        - "Yes"
27        - "No"
28    validations:
29      required: true
30  - type: textarea
31    id: description
32    attributes:
33      label: Description
34      description: |
35        Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see above).
36    validations:
37      required: true
38  - type: input
39    id: forgejo-ver
40    attributes:
41      label: Forgejo Version
42      description: Forgejo version (or commit reference) of your instance
43  - type: input
44    id: runner-ver
45    attributes:
46      label: Runner Version
47      description: Runner version (or commit reference) of the runner on your instance
48  - type: textarea
49    id: forgejo-run-info
50    attributes:
51      label: How are you running Forgejo?
52      description: |
53        Please include information on whether you built Forgejo yourself, used one of our downloads, or are using some other package.
54        Please also tell us how you are running Forgejo, e.g. if it is being run from a container, a command-line, systemd etc.
55        If you are using a package or systemd tell us what distribution you are using.
56    validations:
57      required: true
58  - type: textarea
59    id: runner-run-info
60    attributes:
61      label: How are you running the Runner?
62      description: |
63        Please include information on whether you built the Runner yourself, used one of our downloads, or are using some other package.
64        Please also tell us how you are running it, e.g. if it is being run from a container, a command-line, systemd etc.
65        If you are using a package or systemd tell us what distribution you are using.
66    validations:
67      required: true
68  - type: textarea
69    id: logs
70    attributes:
71      label: Logs
72      description: |
73        It's really important to provide pertinent logs. You must give us `DEBUG` level logs.
74        Please read https://forgejo.org/docs/latest/admin/logging-documentation/.
75
76        Please copy and paste your logs here, with any sensitive information (e.g. API keys) removed/hidden.
77        You can wrap your logs in `<details>...</details>` tags so it doesn't take up too much space in the issue.
78  - type: textarea
79    id: workflow
80    attributes:
81      label: Workflow file
82      description: |
83        If the bug occurs in a specific workflow, please provide an example workflow file.
84        If you have linked to a reproduction repository this won't be necessary.