Augment existing Github Problem Matcher for `go test ./...` output

Open
#681 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, go
Domain
ci-cd, testing-qa

Research direction

Begin with the existing matchers.json referenced in the issue and compare its current Go matcher with the problem-matcher documentation linked there. Exercise it against go test ./... output; the work is done when Go test failures appear inline in the PR files view alongside existing lint findings.

Written by the indexing model from the issue text.

Description

feature request

Description:
Add a github problem matcher to match go test ./... output, matching any go test failures.

Justification:
I would like to be able to see test failures inline in the PR files view, just like how go lints will show up.

Are you willing to submit a PR?

Sure, if there's some feedback

Refs:

Dominant language
TypeScript
Stars
1.8k
Forks
684
Avg merge
12d 23h
Merged PRs (30d)
3

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/setup-go

All issues in actions/setup-go

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.