diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..db44d7e5 --- /dev/null +++ b/.github/CODE_OF_CONDUCT.md @@ -0,0 +1,3 @@ +# Code of conduct + +- [Moby community guidelines](https://github.com/moby/moby/blob/master/CONTRIBUTING.md#moby-community-guidelines) diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml new file mode 100644 index 00000000..2a8c6ef3 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug.yml @@ -0,0 +1,101 @@ +# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema +name: Bug Report +description: Report a bug +labels: + - status/triage + +body: + - type: markdown + attributes: + value: | + Thank you for taking the time to report a bug! + If this is a security issue please report it to the [Docker Security team](mailto:security@docker.com). + + - type: checkboxes + attributes: + label: Contributing guidelines + description: > + Make sure you've read the contributing guidelines before proceeding. + options: + - label: I've read the [contributing guidelines](https://github.com/docker/setup-qemu-action/blob/master/.github/CONTRIBUTING.md) and wholeheartedly agree + required: true + + - type: checkboxes + attributes: + label: "I've found a bug, and:" + description: | + Make sure that your request fulfills all of the following requirements. + If one requirement cannot be satisfied, explain in detail why. + options: + - label: The documentation does not mention anything about my problem + - label: There are no open or closed issues that are related to my problem + + - type: textarea + attributes: + label: Description + description: > + Provide a brief description of the bug in 1-2 sentences. + validations: + required: true + + - type: textarea + attributes: + label: Expected behaviour + description: > + Describe precisely what you'd expect to happen. + validations: + required: true + + - type: textarea + attributes: + label: Actual behaviour + description: > + Describe precisely what is actually happening. + validations: + required: true + + - type: input + attributes: + label: Repository URL + description: > + Enter the URL of the repository where you are experiencing the + issue. If your repository is private, provide a link to a minimal + repository that reproduces the issue. + + - type: input + attributes: + label: Workflow run URL + description: > + Enter the URL of the GitHub Action workflow run if public (e.g. + `https://github.com///actions/runs/`) + + - type: textarea + attributes: + label: YAML workflow + description: | + Provide the YAML of the workflow that's causing the issue. + Make sure to remove any sensitive information. + render: yaml + validations: + required: true + + - type: textarea + attributes: + label: Workflow logs + description: > + [Attach](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files) + the [log file of your workflow run](https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#downloading-logs) + and make sure to remove any sensitive information. + + - type: textarea + attributes: + label: BuildKit logs + description: > + If applicable, provide the [BuildKit container logs](https://docs.docker.com/build/ci/github-actions/configure-builder/#buildkit-container-logs) + render: text + + - type: textarea + attributes: + label: Additional info + description: | + Provide any additional information that could be useful. diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md deleted file mode 100644 index d50d1096..00000000 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -name: Bug report -about: Create a report to help us improve ---- - -### Behaviour - -#### Steps to reproduce this issue - -1. -2. -3. - -#### Expected behaviour - -> Tell us what should happen - -#### Actual behaviour - -> Tell us what happens instead - -### Configuration - -* Repository URL (if public): -* Build URL (if public): - -```yml -# paste your YAML workflow file here and remove sensitive data -``` - -### Logs - -> Download the [log file of your build](https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#downloading-logs) -> and [attach it](https://docs.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) to this issue. diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 00000000..c9050493 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,9 @@ +# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser +blank_issues_enabled: true +contact_links: + - name: Questions and Discussions + url: https://github.com/docker/setup-qemu-action/discussions/new + about: Use Github Discussions to ask questions and/or open discussion topics. + - name: Documentation + url: https://docs.docker.com/build/ci/github-actions/ + about: Read the documentation. diff --git a/.github/ISSUE_TEMPLATE/feature.yml b/.github/ISSUE_TEMPLATE/feature.yml new file mode 100644 index 00000000..6ab75684 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature.yml @@ -0,0 +1,15 @@ +# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema +name: Feature request +description: Missing functionality? Come tell us about it! +labels: + - kind/enhancement + - status/triage + +body: + - type: textarea + id: description + attributes: + label: Description + description: What is the feature you want to see? + validations: + required: true diff --git a/.github/SECURITY.md b/.github/SECURITY.md new file mode 100644 index 00000000..e8398953 --- /dev/null +++ b/.github/SECURITY.md @@ -0,0 +1,12 @@ +# Reporting security issues + +The project maintainers take security seriously. If you discover a security +issue, please bring it to their attention right away! + +**Please _DO NOT_ file a public issue**, instead send your report privately to +[security@docker.com](mailto:security@docker.com). + +Security reports are greatly appreciated, and we will publicly thank you for it. +We also like to send gifts—if you'd like Docker swag, make sure to let +us know. We currently do not offer a paid security bounty program, but are not +ruling it out in the future. diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md deleted file mode 100644 index 04e485a1..00000000 --- a/.github/SUPPORT.md +++ /dev/null @@ -1,31 +0,0 @@ -# Support [![](https://isitmaintained.com/badge/resolution/docker/setup-qemu-action.svg)](https://isitmaintained.com/project/docker/setup-qemu-action) - -First, [be a good guy](https://github.com/kossnocorp/etiquette/blob/master/README.md). - -## Reporting an issue - -Please do a search in [open issues](https://github.com/docker/setup-qemu-action/issues?utf8=%E2%9C%93&q=) to see if the issue or feature request has already been filed. - -If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment. - -:+1: - upvote - -:-1: - downvote - -If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below. - -## Writing good bug reports and feature requests - -File a single issue per problem and feature request. - -* Do not enumerate multiple bugs or feature requests in the same issue. -* Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes. - -The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. - -You are now ready to [create a new issue](https://github.com/docker/setup-qemu-action/issues/new/choose)! - -## Closure policy - -* Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines. -* Issues that go a week without a response from original poster are subject to closure at our discretion.