Epic: CI/CD cleanup (husky, releases, tests, speed)
Open
Nobody has claimed this yet.
wizard-pain
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Tracking issue for the CI/CD cleanup cluster. These were filed separately but form one theme. They can mostly run in parallel; one pair must be chained.
Work items
- #546 — Husky pre-commit hooks (quick win, independent)
- #545 — Release automation (independent)
- #547 — More integration tests (independent)
- #568 — Rip the monorepo + MCP out of CI/CD ⟶ prerequisite for #559
- #559 — CI takes too long ⟶ depends on #568
Dispatch notes
- Parallel-safe: #546, #545, #547 touch different areas — one agent each, separate worktrees.
- Chain: #568 → #559. Removing the monorepo from CI is part of the speedup, so sequence them under one owner rather than running both at once.
Each child keeps its own priority label; this epic is just the tracker.
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.
Research direction
Start by reading child issues #546, #545, #547, #568, and #559, following the stated dependency from #568 to #559. This epic is done when all listed work items are completed and the CI/CD cleanup cluster is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd, release, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100