Problem matchers which match an invalid file cause annotations to come up as being in the file .github
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
If a problem matcher doesn't match a valid file (e.g. the regex captures "test.txt ", with a space at the end, the annotation comes up as being in the file .github rather than the matched file.
To Reproduce
Create a problem matcher which matches at least an invalid filename, or possibly a file not in the repo.
Expected behavior
Either not annotating .github, or annotating the match for a filename that doesn't exist, or perhaps clearest some sort of error somewhere (perhaps in the action log), that the matched filename doesn't exist.
Contributor 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.
Research direction
No file or test is named in the report. Reproduce the problem with a matcher whose filename capture has a trailing space or names a missing file, then trace how the toolkit turns that match into an annotation. Done means invalid paths no longer produce a misleading .github annotation, with behavior covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100