Add a Makefile
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- build-system
Research direction
Read .github/workflows/ci.yml and the README or CONTRIBUTING instructions to identify the current CI steps and where contributor setup is documented. Add a root Makefile with the requested build, test, vet, formatting, and check targets, then update the contributor documentation to mention make check. Done means make check matches CI, and make build and make test work on macOS and Linux.
Written by the indexing model from the issue text.
Description
What
Contributors run four commands by hand (go build ./..., go vet ./..., go test ./..., gofmt -l .). Wrap them in a Makefile.
Where
New file: Makefile
Suggested targets
make build→go build ./...make test→go test ./...make vet→go vet ./...make fmt→ format, or checkgofmt -l .make check→ vet + fmt-check + test (the CI contract)
Done when
-
make checkruns the same steps as.github/workflows/ci.yml -
make buildandmake testwork on macOS and Linux - README/CONTRIBUTING mention
make check
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- Avg merge
- 1h 31m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 Edwin-metcalf/MetCode
-
documentation enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Edwin-metcalf/MetCode#19 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Edwin-metcalf/MetCode#18 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Edwin-metcalf/MetCode#16 ·
-
testing
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Edwin-metcalf/MetCode#9 ·
-
Add a --host flagOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Edwin-metcalf/MetCode#7 ·
All issues in Edwin-metcalf/MetCode
Similar issues
-
documentation hacktoberfest priority: low skill: good first issue status: ready for dev
Difficulty 2/5 Half a day Newbie friendliness 85/100
hyperledger-labs/fabric-smart-client#2142 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
numberly/vault-db-injector#107 ·
Maintainers usually reply within 1 day
-
area/import kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[DOC] Wrong sg_egress_ports range in the Terraform Databricks Guide for AWS Hub & Spoke with Network FirewallPossibly taken @akhil9tiet claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
databricks/terraform-provider-databricks#6080 · 1 comment ·
Maintainers usually reply within 3 days
-
kind/documentation
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
kubernetes-sigs/dra-driver-nvidia-gpu#1569 ·
Maintainers usually reply within 1 day