9343fd413b
* Repository maintenance: add GitHub Repo Gardening action The Repo Gardening action is a tool that one can use to automate some of the tasks that you can perform to monitor activity in your repository. https://github.com/marketplace/actions/repository-gardening It includes different tasks, that can be enabled based on your needs. This commit gets us started with the action by enabling a few tasks. - This action relies on a few secrets that have already been added to this repo. - Of note, `gatherSupportReferences` and `replyToCustomersReminder` aren't too useful right now, but will become useful once the plugin is released on WordPress.com and once we start receiving feedback from WordPress.com site owners. - The `flagOss` task will point to #fediverse for now. This can be updated later on. - I've added mapping for our 2 block directories, but that mapping can be extended for more automatic labeling later on. * Add issue templates
90 lines
2.2 KiB
YAML
90 lines
2.2 KiB
YAML
name: Bug Report
|
|
description: Helps us improve our product!
|
|
labels: "Needs triage, [Type] Bug"
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
### Thanks for contributing!
|
|
|
|
Please write a clear title, then fill in the fields below and submit.
|
|
|
|
Please **do not** link to image hosting services such as Cloudup, Droplr, Imgur, etc…
|
|
Instead, directly embed screenshot(s) or recording(s) in any of the text areas below: click, then drag and drop.
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
---
|
|
## Core Information
|
|
- type: textarea
|
|
id: summary
|
|
attributes:
|
|
label: Quick summary
|
|
- type: textarea
|
|
id: steps
|
|
attributes:
|
|
label: Steps to reproduce
|
|
placeholder: |
|
|
1. Start at `site-domain.com/blog`.
|
|
2. Click on any blog post.
|
|
3. ...
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: expected
|
|
attributes:
|
|
label: What you expected to happen
|
|
placeholder: |
|
|
e.g. The post should appear.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: actual
|
|
attributes:
|
|
label: What actually happened
|
|
placeholder: |
|
|
e.g. The post did not appear.
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: users-affected
|
|
attributes:
|
|
label: Impact
|
|
description: Approximately how many users are impacted?
|
|
options:
|
|
- One
|
|
- Some (< 50%)
|
|
- Most (> 50%)
|
|
- All
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: workarounds
|
|
attributes:
|
|
label: Available workarounds?
|
|
options:
|
|
- No and the platform is unusable
|
|
- No but the platform is still usable
|
|
- Yes, difficult to implement
|
|
- Yes, easy to implement
|
|
- There is no user impact
|
|
validations:
|
|
required: true
|
|
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
<br>
|
|
|
|
## Optional Information
|
|
|
|
The following section is optional.
|
|
- type: textarea
|
|
id: logs
|
|
attributes:
|
|
label: Logs or notes
|
|
placeholder: |
|
|
Add any information that may be relevant, such as:
|
|
- Browser/Platform
|
|
- Theme
|
|
- Logs/Errors
|