ci: bot report workflows match any open issue by label and title, so a user-opened issue can capture the weekly report
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
Research direction
Read the issue lookup commands in .github/workflows/links.yml, .github/workflows/reverify.yml, and .github/workflows/thumbs.yml. Verify each lookup only selects bot-authored issues, and that a user-opened issue with a matching title and label is ignored.
Written by the indexing model from the issue text.
Description
Why it matters
The weekly link check, the monthly re-verify batch and the thumbnail report each find "their" issue by label and title prefix only. Any GitHub user can open an issue that matches. The bot then writes its report into that user's issue instead of the real one (currently #162). Report history ends up split, and the issue's author can rewrite the text the maintainer relies on.
Evidence
.github/workflows/links.yml:42:gh issue list --state open --label correction ..., then a titlestartswith("Link check:")filter..github/workflows/reverify.yml:41and.github/workflows/thumbs.yml:62use the same pattern.
.github/ISSUE_TEMPLATE/correction.yml applies the correction label automatically, and the title is free text.
Suggested approach
Add --author app/github-actions to each lookup, so only bot-authored issues match.
Done when
All three workflows filter by author. A user-opened issue with a matching title and label is ignored.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 15
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/Free-Game-Dev-Assets
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#178 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#176 ·
Maintainers usually reply within 1 day
-
copy: headline and README badge count 418 including 2 deprecated entries; the catalog shows 416Openbug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TMHSDigital/Free-Game-Dev-Assets#175 ·
Maintainers usually reply within 1 day
-
enhancement priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
TMHSDigital/Free-Game-Dev-Assets#174 ·
Maintainers usually reply within 1 day
-
bug hardening priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#170 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/Free-Game-Dev-Assets
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
riverqueue/river#1576 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modrollstudio/Modroll-Studio-Website#80 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mafzalkalwardev/mailforge#21 ·
-
good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 82/100