[Chore] Add CI for Go test and build
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Start by checking the repository layout and GitHub Actions workflow conventions, then run go test ./... and go build ./... locally to confirm the commands. Add a workflow under .github/workflows that runs on pushes and pull requests; done means both commands pass in CI.
Written by the indexing model from the issue text.
Description
Add GitHub Actions workflow to validate build and tests on PRs.\n\nAcceptance Criteria:\n- [ ] Run go test ./...\n- [ ] Run go build ./...\n- [ ] Trigger on push and PR\n
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from everbee7/telegram-forward-go
-
priority:high type:feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
priority:medium type:feature
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
priority:high type:feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in everbee7/telegram-forward-go
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100