Annotation matcher can not match column ranges
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 673
- Avg merge
- 6d 28m
- Merged PRs (30d)
- 4
Description
Description:
Tools like gopls check <files> can output line column ranges but the matcher installed by this action can not match them.
This action can not match these column ranges because the - character is not included in the regex ^\\s*(.+\\.go):(?:(\\d+):(\\d+):)? (.*). All such lines in this sample run should trigger a error annotation, but currently ones ones without a - trigger it:
Action version:
v5.0.0
Platform:
all
Runner type:
all
Tools version:
all
Repro steps:
https://github.com/go-gitea/gitea/actions/runs/8883003671/job/24388906594
Expected behavior:
Lines with - in the column field to be detected as error annotation.
Actual behavior:
Only lines without - in the column are detected as error annotation.
Contributor guide
No contributing guide indexed for this repository
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
Start with matchers.json and inspect the annotation matcher regex against the gopls output shown in the linked sample run. Verify that column ranges containing a hyphen are detected as error annotations, while existing lines without a hyphen continue to match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100