adoptium / adoptium/infrastructure
Labelling bot seems unable to identify Windows issues
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
We should look at the labeller bot and ensure that it can correctly identify issues relating to Windows and tag them with `os:windows`. I've just added that label to a few issues manually.
Noting that the following is not the same list:
- [Search for `Windows`](https://github.com/adoptium/infrastructure/issues?q=is%3Aissue%20state%3Aopen%20windows)
- [`os:windows` label](https://github.com/adoptium/infrastructure/issues?q=is%3Aissue%20state%3Aopen%20windows%20label%3Aos%3Awindows)
Also noting that the above list includes quite a lot more as some things (such as [the new machine template](https://github.com/adoptium/infrastructure/blob/master/.github/ISSUE_TEMPLATE/newmachine.md)) includes `windows` in the example list of operating systems so it perhaps needs be looking for `windows` without `/` around it. This is probably true of some of the others os/arch labelling too so a general review might be in order.
Contributor guide
Research direction
Start by locating the labeller bot and comparing its matching behavior with the open-issue search and the `os:windows` label results. Review `.github/ISSUE_TEMPLATE/newmachine.md` as a known source of false or missed matches, then verify that relevant Windows issues receive `os:windows` without incorrectly tagging unrelated issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100