Skip to content
This repository was archived by the owner on Aug 1, 2024. It is now read-only.

Commit c037524

Browse files
authored
chore: Add comment to bug reports. (#1089)
This workflow adds a follow-up checklist for arch-bom developers to use when triaging bugs. edx/edx-arch-experiments#310
1 parent d4875e8 commit c037524

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: Add comment
2+
on:
3+
issues:
4+
types:
5+
- labeled
6+
jobs:
7+
add-comment:
8+
if: github.event.label.name == 'bug'
9+
runs-on: ubuntu-latest
10+
permissions:
11+
issues: write
12+
steps:
13+
- name: Add comment
14+
uses: peter-evans/create-or-update-comment@5f728c3dae25f329afbe34ee4d08eef25569d79f
15+
with:
16+
issue-number: ${{ github.event.issue.number }}
17+
body: |
18+
Follow-up checklist (for Arch-BOM usage)
19+
- [ ] Is the issue flaky or consistent?
20+
- [ ] Does it affect multiple people or multiple types of systems?
21+
- [ ] Update the devstack troubleshooting documentation page if necessary
22+
- [ ] Do we need a new troubleshooting section?
23+
- [ ] Did a troubleshooting section already exist, but it wasn't easy to find given the symptoms?
24+
- [ ] If a recurring issue, should we ticket an automated resolution in place of the doc?

0 commit comments

Comments
 (0)