init --verification-workflow: the generated workflow never installs dependencies, so verify cannot run the tests

Open
#296 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@FredApps is already working on this.

Since Nov 17, 2026.

  • #297 by @FredApps — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
github-actions, node.js, typescript
Domain
ci-cd, tooling

Research direction

Start with packages/diffci-cli/src/client/workflow-templates.ts and inspect the diffciVerificationWorkflow template. Reproduce with a project that has vitest in devDependencies and a package-lock.json, then check the generated workflow’s steps. Done means it installs dependencies with npm ci before “Verify changed code” and the test command runs.

Written by the indexing model from the issue text.

Description

diffci init --verification-workflow writes a workflow (diffciVerificationWorkflow in packages/diffci-cli/src/client/workflow-templates.ts) that checks out the repository, sets up Node and runs diffci verify. It never installs the repository's dependencies. verify runs the repository's own tests, so in any project whose test runner is a dev dependency the job fails before a test runs.

Repro: a project with vitest in devDependencies, a package-lock.json and "test": "vitest run". Run diffci init --verification-workflow and run the generated workflow, or run diffci verify in a fresh checkout without npm ci.

Expected: the workflow installs dependencies (npm ci here) before "Verify changed code", and the tests run.

Actual: there is no install step. verify FAILED, and the test command printed "npx canceled due to missing packages" (vitest not installed).

Not covered here: a repository whose package manager DiffCI cannot detect, and Bun.

Dominant language
TypeScript
Stars
0
Forks
4
Avg merge
18h 41m
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DiffCI/core

All issues in DiffCI/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.