Process scripts are covered by tests that run in CI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reading the scripts named in the issue: roadmap.py, sprint.py, conventions.py, check_task_ids.py, i18n.py, and project_state.py, along with their existing tests and the project’s test and CI configuration. Add offline tests in tests/process/ that cover the listed rules, then run uv run just check and confirm the tests finish in under ten seconds. Done means removing any rule causes a test failure and CI runs the process tests.
Written by the indexing model from the issue text.
Description
Part of #136. Milestone gate: wayloop init on an empty repository produces a structure that passes wayloop validate.
Outcome
The rules of the process are code: roadmap, sprints, commit conventions, task ids, translations and the session briefing. Today they run without tests, so a change to a script can silently stop enforcing a rule, and every later pull request would pass a check that no longer checks.
Scope
- Tests in
tests/process/forroadmap.py: canonical form, unique issues, specs that exist and are referenced, releases in order, the pull request body that closes a planned task - Tests for
sprint.py: lanes with disjoint paths, generated files in one lane, shared state across worktrees, a pull request that leaves its lane - Tests for
conventions.py: types, scopes, subject rules, bot commits - Tests for
check_task_ids.py,i18n.pyandproject_state.py - pytest in the dev group;
just processruns the tests; a CI step runs them
Acceptance criteria
- Removing any rule from a script makes at least one test fail
- The tests run offline and in less than ten seconds
Delivery
PR 1 of the process parity epic: PR 1 tests, forms and title checks; PR 2 bootstrap, required checks, security and maintenance; PR 3 hooks, documentation sync and automated review.
Definition of done
- Tests written first for every rule the change adds
-
uv run just checkpasses locally and CI is green - The conventions or contributing page updated where a rule changes; Italian edition stamped where the page is translated
- The task is marked
doneinroadmap/roadmap.yamlin the same pull request, whose body saysCloses #137 - Review proportional to risk (AGENTS.md): every finding fixed in the same pull request
Generated by Claude Code
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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 salvo8519/wayloop
-
area:docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area:infra
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
area:infra
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
area:infra
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
area:infra epic
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in salvo8519/wayloop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btclib-org/btclib-wallet#1045 ·
Maintainers usually reply within 1 day
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[Train] An elastic ScalingConfig(num_workers=(0, 0)) is accepted and the run waits foreverPossibly taken @wguo7 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ray-project/ray#68217 ·
Maintainers usually reply within 2 days