Concider folding lint workflow files into one
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, github-actions
- Domain
- ci-cd
Research direction
The payload names the lint checks to merge: codespell, shellchecker, clang-format, and the sign-off and link trailer checks, but not the workflow file paths. Find the existing lint workflows in the repository's CI configuration first. The issue proposes one job with checkout as a fatal step and the other steps logging errors without stopping, and the job failing if any lint step fails. Ask the maintainers whether that failure policy is wanted before you start.
Written by the indexing model from the issue text.
Description
Currently we have a number of lint stages and we're likely to get more. Namely:
- codespell
- shellchecker
- clang-format
- s-o-b trailer - see link
- link trailer - people are occasionally misusing it
For some piece of mind, sanity and reduce(d) CI resources we can fold the lot roughly as:
- single job - no need for parallelism, the git checkout is already the majority of the CI run
- steps -> checkout, codespell, shellchecker....
- checkout is fatal, other steps log an error and continue
- the whole job fails, if any of the steps fail
- Dominant language
- C
- Stars
- 116
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
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 kmod-project/kmod
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kmod-project/kmod#492 ·
Maintainers usually reply within 4 days
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
kmod-project/kmod#483 ·
Maintainers usually reply within 4 days
-
Various 34.x backport nominationsPossibly taken @lucasdemarchi claimed this 5 days ago. Openfor-lucas
kmod-project/kmod#480 · 2 comments · 1 assignee ·
Maintainers usually reply within 4 days
-
Use `malloc` function attributePossibly taken @crims0n claimed this 4 days ago. Opengood first issue
Difficulty 3/5 1-2 days Newbie friendliness 52/100
kmod-project/kmod#479 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
kmod-project/kmod#476 · 1 comment ·
Maintainers usually reply within 4 days
All issues in kmod-project/kmod
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PecanProject/sipnet#435 · 1 comment ·
Maintainers usually reply within 2 days
-
SDL_GPU Vulkan: wrong screen orientation on OpenHarmony (preTransform set without pre-rotation)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
libsdl-org/SDL#16670 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
要トリアージ 辞書
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yksr-melt/Meltype#1625 · 1 reaction ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day