chore: Convert templates to YAML issue forms
This commit is contained in:
peaceiris
parent
20d6724b2c
commit
5fb41c87da
6 changed files with 149 additions and 101 deletions
36
.github/ISSUE_TEMPLATE/1_user_support.md
vendored
36
.github/ISSUE_TEMPLATE/1_user_support.md
vendored
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
name: User Support
|
||||
about: Questions for this Action
|
||||
title: 'sample_title'
|
||||
labels: support
|
||||
assignees: peaceiris
|
||||
---
|
||||
|
||||
**Note that an issue which does not follow the template will be closed silently.**
|
||||
|
||||
## Check list before opening this issue
|
||||
|
||||
- [ ] I read the latest README of this repository.
|
||||
|
||||
For users of the GitHub Pages Action:
|
||||
|
||||
- [ ] I checked [Available Options](https://github.com/peaceiris/actions-gh-pages#options)
|
||||
- [ ] I followed [Tips and FAQs](https://github.com/peaceiris/actions-gh-pages#tips-and-faq)
|
||||
- [ ] I tried [Workflow Examples](https://github.com/peaceiris/actions-gh-pages#examples)
|
||||
|
||||
## Describe your question
|
||||
|
||||
A clear and concise description of what the question is.
|
||||
|
||||
## Link to your contents
|
||||
|
||||
- Link to your public repository here
|
||||
- Link to your workflow here
|
||||
|
||||
## Screenshots
|
||||
|
||||
If applicable, add screenshots to help explain your question.
|
||||
|
||||
## Additional context
|
||||
|
||||
Add any other context about the problem here.
|
||||
52
.github/ISSUE_TEMPLATE/1_user_support.yml
vendored
Normal file
52
.github/ISSUE_TEMPLATE/1_user_support.yml
vendored
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
name: User Support
|
||||
description: Questions for this action
|
||||
title: "support: "
|
||||
labels: support
|
||||
assignees: peaceiris
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value:
|
||||
Please note we will close your issue without comment if you do not fill out the issue checklist below and provide ALL the requested information.
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Checklist
|
||||
description: Checklist before creating an issue.
|
||||
options:
|
||||
- label: "I am using the latest version of this aciton."
|
||||
required: true
|
||||
- label: "I have read the latest README and followed the instructions."
|
||||
required: true
|
||||
- label: "I have read the latest GitHub Actions official documentation and learned the basic spec and concepts."
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Describe your question
|
||||
description: A clear and concise description of what the question is.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Relevant links
|
||||
description:
|
||||
Links to your public repository, YAML config file, and YAML workflow file.
|
||||
Please use [a permanent link](https://docs.github.com/en/github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files), not a default branch.
|
||||
render: markdown
|
||||
value: |
|
||||
Public repository:
|
||||
YAML config:
|
||||
YAML workflow:
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Relevant log output
|
||||
description: Copy and paste any relevant log output here.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Additional context.
|
||||
description: Write any other context about the question here.
|
||||
validations:
|
||||
required: true
|
||||
39
.github/ISSUE_TEMPLATE/2_bug_report.md
vendored
39
.github/ISSUE_TEMPLATE/2_bug_report.md
vendored
|
|
@ -1,39 +0,0 @@
|
|||
---
|
||||
name: Bug Report
|
||||
about: First, use the User Support Issue Template
|
||||
title: 'sample_title'
|
||||
labels: bug
|
||||
assignees: peaceiris
|
||||
|
||||
---
|
||||
|
||||
**Note that an issue which does not follow the template will be closed silently.**
|
||||
|
||||
## Describe the bug
|
||||
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
## To Reproduce
|
||||
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
## Expected behavior
|
||||
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
## Screenshots
|
||||
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
## Your YAML file
|
||||
|
||||
- A link to your repository
|
||||
- A link to your YAML file
|
||||
|
||||
## Additional context
|
||||
|
||||
Add any other context about the problem here.
|
||||
52
.github/ISSUE_TEMPLATE/2_bug_report.yml
vendored
Normal file
52
.github/ISSUE_TEMPLATE/2_bug_report.yml
vendored
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
name: Bug Report
|
||||
description: Try the User Support Issue Template first.
|
||||
title: 'bug: '
|
||||
labels: bug
|
||||
assignees: peaceiris
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value:
|
||||
Please note we will close your issue without comment if you do not fill out the issue checklist below and provide ALL the requested information.
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Checklist
|
||||
description: Checklist before creating an issue.
|
||||
options:
|
||||
- label: "I am using the latest version of this aciton."
|
||||
required: true
|
||||
- label: "I have read the latest README and followed the instructions."
|
||||
required: true
|
||||
- label: "I have read the latest GitHub Actions official documentation and learned the basic spec and concepts."
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "Describe the bug"
|
||||
description: "A clear and concise description of what the bug is."
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Relevant links
|
||||
description:
|
||||
Links to your public repository, YAML config file, and YAML workflow file.
|
||||
Please use [a permanent link](https://docs.github.com/en/github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files), not a default branch.
|
||||
render: markdown
|
||||
value: |
|
||||
Public repository:
|
||||
YAML config:
|
||||
YAML workflow:
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Relevant log output
|
||||
description: Copy and paste any relevant log output here.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Additional context.
|
||||
description: Write any other context about the question here.
|
||||
validations:
|
||||
required: true
|
||||
26
.github/ISSUE_TEMPLATE/3_proposal.md
vendored
26
.github/ISSUE_TEMPLATE/3_proposal.md
vendored
|
|
@ -1,26 +0,0 @@
|
|||
---
|
||||
name: Proposal
|
||||
about: Suggest an idea for this project
|
||||
title: 'sample_title'
|
||||
labels: proposal
|
||||
assignees: peaceiris
|
||||
|
||||
---
|
||||
|
||||
**Note that an issue which does not follow the template will be closed silently.**
|
||||
|
||||
## Is your feature request related to a problem? Please describe.
|
||||
|
||||
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
|
||||
|
||||
## Describe the solution you'd like
|
||||
|
||||
A clear and concise description of what you want to happen.
|
||||
|
||||
## Describe alternatives you've considered
|
||||
|
||||
A clear and concise description of any alternative solutions or features you've considered.
|
||||
|
||||
## Additional context
|
||||
|
||||
Add any other context or screenshots about the feature request here.
|
||||
45
.github/ISSUE_TEMPLATE/3_proposal.yml
vendored
Normal file
45
.github/ISSUE_TEMPLATE/3_proposal.yml
vendored
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
name: Proposal
|
||||
description: Suggest an idea for this project
|
||||
title: 'proposal: '
|
||||
labels: proposal
|
||||
assignees: peaceiris
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value:
|
||||
Please note we will close your issue without comment if you do not fill out the issue checklist below and provide ALL the requested information.
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Checklist
|
||||
description: Checklist before creating an issue.
|
||||
options:
|
||||
- label: "I am using the latest version of this aciton."
|
||||
required: true
|
||||
- label: "I have read the latest README and followed the instructions."
|
||||
required: true
|
||||
- label: "I have read the latest GitHub Actions official documentation and learned the basic spec and concepts."
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "Describe your proposal"
|
||||
description: "A clear and concise description of what the proposal is."
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "Describe the solution you'd like"
|
||||
description: "A clear and concise description of what you want to happen."
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "Describe alternatives you've considered"
|
||||
description: "A clear and concise description of any alternative solutions or features you've considered."
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: "Additional context"
|
||||
description: "Add any other context or screenshots about the feature request here."
|
||||
validations:
|
||||
required: true
|
||||
Loading…
Reference in a new issue