Augment existing Github Problem Matcher for `go test ./...` output
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
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
- 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 actions/setup-go
-
Provide an option to skip the Go SDK tool-cache write for ephemeral / parallel self-hosted runnersOpenfeature request
Difficulty 3/5 1-2 days Newbie friendliness 72/100
actions/setup-go#792 · 4 comments ·
Maintainers usually reply within 5 days
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
actions/setup-go#757 · 2 comments ·
Maintainers usually reply within 5 days
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 55/100
actions/setup-go#749 · 2 comments ·
Maintainers usually reply within 5 days
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 58/100
actions/setup-go#746 · 8 comments ·
Maintainers usually reply within 5 days
-
go-version-file does not parse .mod files other than go.modPossibly taken @kaovilai claimed this 239 days ago. Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
actions/setup-go#736 · 1 comment · 1 reaction ·
Maintainers usually reply within 5 days
All issues in actions/setup-go
Similar issues
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
device-management-toolkit/sample-web-ui#3711 ·
Maintainers usually reply within 1 day
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPossibly taken @seenimohamed claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ardia-browser/ardia#2769 ·
Maintainers usually reply within 1 day