|
| 1 | +# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema |
| 2 | +name: Bug Report |
| 3 | +description: Report a bug |
| 4 | +labels: |
| 5 | + - status/triage |
| 6 | + |
| 7 | +body: |
| 8 | + - type: markdown |
| 9 | + attributes: |
| 10 | + value: | |
| 11 | + Thank you for taking the time to report a bug! |
| 12 | + If this is a security issue please report it to the [Docker Security team](mailto:[email protected]). |
| 13 | + Before submitting a bug report, check out the [Troubleshooting doc](https://github.com/docker/build-push-action/blob/master/TROUBLESHOOTING.md). |
| 14 | +
|
| 15 | + - type: checkboxes |
| 16 | + attributes: |
| 17 | + label: Contributing guidelines |
| 18 | + description: > |
| 19 | + Make sure you've read the contributing guidelines before proceeding. |
| 20 | + options: |
| 21 | + - label: I've read the [contributing guidelines](https://github.com/docker/build-push-action/blob/master/.github/CONTRIBUTING.md) and wholeheartedly agree |
| 22 | + required: true |
| 23 | + |
| 24 | + - type: checkboxes |
| 25 | + attributes: |
| 26 | + label: "I've found a bug, and:" |
| 27 | + description: | |
| 28 | + Make sure that your request fulfills all of the following requirements. |
| 29 | + If one requirement cannot be satisfied, explain in detail why. |
| 30 | + options: |
| 31 | + - label: The documentation does not mention anything about my problem |
| 32 | + - label: There are no open or closed issues that are related to my problem |
| 33 | + |
| 34 | + - type: textarea |
| 35 | + attributes: |
| 36 | + label: Description |
| 37 | + description: > |
| 38 | + Provide a brief description of the bug in 1-2 sentences. |
| 39 | + validations: |
| 40 | + required: true |
| 41 | + |
| 42 | + - type: textarea |
| 43 | + attributes: |
| 44 | + label: Expected behaviour |
| 45 | + description: > |
| 46 | + Describe precisely what you'd expect to happen. |
| 47 | + validations: |
| 48 | + required: true |
| 49 | + |
| 50 | + - type: textarea |
| 51 | + attributes: |
| 52 | + label: Actual behaviour |
| 53 | + description: > |
| 54 | + Describe precisely what is actually happening. |
| 55 | + validations: |
| 56 | + required: true |
| 57 | + |
| 58 | + - type: input |
| 59 | + attributes: |
| 60 | + label: Repository URL |
| 61 | + description: > |
| 62 | + Enter the URL of the repository where you are experiencing the |
| 63 | + issue. If your repository is private, provide a link to a minimal |
| 64 | + repository that reproduces the issue. |
| 65 | +
|
| 66 | + - type: input |
| 67 | + attributes: |
| 68 | + label: Workflow run URL |
| 69 | + description: > |
| 70 | + Enter the URL of the GitHub Action workflow run, if public. |
| 71 | +
|
| 72 | + - type: textarea |
| 73 | + attributes: |
| 74 | + label: YAML workflow |
| 75 | + description: | |
| 76 | + Provide the YAML of the workflow that's causing the issue. |
| 77 | + Make sure to remove any sensitive information. |
| 78 | + render: yaml |
| 79 | + validations: |
| 80 | + required: true |
| 81 | + |
| 82 | + - type: textarea |
| 83 | + attributes: |
| 84 | + label: Workflow logs |
| 85 | + description: > |
| 86 | + [Attach](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files) |
| 87 | + the [log file of your workflow run](https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#downloading-logs) |
| 88 | + and make sure to remove any sensitive information. |
| 89 | +
|
| 90 | + - type: textarea |
| 91 | + attributes: |
| 92 | + label: BuildKit logs |
| 93 | + description: > |
| 94 | + If applicable, provide the [BuildKit container logs](https://docs.docker.com/build/ci/github-actions/configure-builder/#buildkit-container-logs) |
| 95 | + render: text |
| 96 | + |
| 97 | + - type: textarea |
| 98 | + attributes: |
| 99 | + label: Additional info |
| 100 | + description: | |
| 101 | + Provide any additional information that could be useful. |
0 commit comments