shift-left: dup-ratchet at pre-push, Sonar duplication informative
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github
- Domain
- ci-cd
Research direction
Start by reading ADR-013 and locating the dup-ratchet implementation and the component / duplication CI job in the organization’s shared configuration. Then trace how pre-push hooks and the « Krizaka way » gate are configured. Done means the hook runs the ratchet, the gate change is recorded in ADR-013, and the CI duplication guard remains in place.
Written by the indexing model from the issue text.
Description
Duplication: copy-paste is measured twice, at the same stage: by the component / duplication job (the dup-ratchet, in 9 repos) and by Sonar CPD on new code. Both run in PR CI.
Do: run the dup-ratchet in the pre-push hook, so it is the earlier guard. Then make Sonar's duplication condition informative in the « Krizaka way » gate. Keep the CI job, because hooks can be bypassed.
Acceptance: the hook runs it; the gate change is recorded in ADR-013; no repo loses a duplication guard.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 12m
- Merged PRs (30d)
- 144
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 krizaka/.github
-
paused
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
krizaka/.github#130 · 4 comments ·
Maintainers usually reply within 1 day
-
paused
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
krizaka/.github#124 · 3 comments ·
Maintainers usually reply within 1 day
-
priority:P1 product:krizaka type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
dotCMS/ai-workflows#74 ·
-
area: ci priority: P4 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
shep-pm/shep#1249 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linuxserver/docker-bookstack#302 · 1 comment ·
-
Chart: a failed venv install is marked ready, and the 10Gi venv PVC is too small for itPossibly taken @andyne13 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day