Skip to content

ci: run frontend lint and use npm ci in the frontend job - #65

Draft
sonnymay wants to merge 1 commit into
mainfrom
claude/vibrant-meitner-kdkoag
Draft

sonnymay wants to merge 1 commit into
mainfrom
claude/vibrant-meitner-kdkoag

Conversation

@sonnymay

Copy link
Copy Markdown
Owner

Summary

The CI frontend job only ran npm install + npm run build, so the configured ESLint (npm run lint) never ran on PRs. Added a Lint step and switched to npm ci for lockfile-reproducible installs.

No open PR (#35–#64) or issue touches ci.yml or frontend linting.

Testing

  • npm ci --include=dev && npm run lint passes cleanly on main.
  • npm run build succeeds.

Generated by Claude Code

The frontend job only built the app, so ESLint (already configured and
passing) never ran on PRs. Add an explicit lint step and switch to
npm ci for reproducible installs from the lockfile.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0171zWzkDbR22w7C5P8peBSZ
@vercel

vercel Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
supportops Ready Ready Preview Oct 31, 2026 2:08pm UTC

This branch was successfully deployed

1 active deployment
Preview — 6fbac93e Deployed Oct 31, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant