CI: Linting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by researching standard Go linting tools and best practices, then inspect the repository's GitHub Actions configuration. Define the selected linter and configure it to run for every pull request; done means the workflow executes successfully and reports lint failures.
Written by the indexing model from the issue text.
Description
Research the linting tools for Golang. What's the standard, and best practices. Propose and implement it as GH Actions so we'll have a linter running for every PR.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from bitovi/bitops-cli
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitovi/bitops-cli#8 ·
-
CI: Unit Tests OpenCI/CD feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bitovi/bitops-cli#6 ·
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bitovi/bitops-cli#4 ·
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitovi/bitops-cli#3 ·
-
CI/CD feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bitovi/bitops-cli#2 ·
All issues in bitovi/bitops-cli
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
needs-triage🔍
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·