Skip to content

Add MIT license, CI workflow, and live demo link#1

Merged
sudo-devKm merged 2 commits into
mainfrom
claude/license-ci-demo-link
Jul 5, 2026
Merged

Add MIT license, CI workflow, and live demo link#1
sudo-devKm merged 2 commits into
mainfrom
claude/license-ci-demo-link

Conversation

@sudo-devKm

@sudo-devKm sudo-devKm commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Added a LICENSE file (MIT) — the repo previously had none, and the README explicitly noted this
  • Added .github/workflows/ci.yml: builds the backend and lints + builds the frontend on push/PR to main
  • Added CI, License, and Live Demo badges to the top of the README, linking the live deployment at https://chat-sphere-tawny.vercel.app/
  • Fixed a typo in frontend/eslint.config.js (no-unused-varno-unused-vars) that was silently crashing ESLint before it could run at all
  • With ESLint actually running, fixed the 22 real lint errors it surfaced (pre-existing, unrelated to the above): React Compiler-related hooks/refs violations, setState-in-effect patterns rewritten to the React-recommended "adjust state during render" pattern, a file split for SocketProvider/Toast to satisfy fast-refresh's one-component-per-file rule, and two unsafe non-null-assertions on optional chains. Two tanstack-virtual measureElement ref assignments are suppressed with an explanatory comment rather than rewritten, since that's the library's documented API, not an unsafe ref read.
  • Supplied build-time env vars in the CI workflow and added a missing frontend/.env.example, since vite.config.ts validates required env vars at build time and exits if they're absent

Test plan

  • npm run lint in frontend/: 0 errors (13 pre-existing warnings, unchanged in scope)
  • npm run build in frontend/ with the same env vars as CI: builds successfully
  • Confirmed via the real GitHub Actions run that the backend job (npm ci && npm run build) already passes
  • CI workflow runs on this PR

Adds a LICENSE file, a GitHub Actions workflow that builds the backend
and lints/builds the frontend on push and PR, and links the live demo
deployment in the README.
@vercel

vercel Bot commented Jul 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
chat-sphere Ready Ready Preview, Comment Jul 5, 2026 1:18pm

- Fix typo in eslint.config.js (no-unused-var -> no-unused-vars) that
  was crashing ESLint before it could even run.
- With ESLint working, fix the 22 real errors it surfaced:
  - Reorder useCall.ts helpers to remove forward references, and
    memoize getPeerConnection so the React Compiler can verify
    acceptCall's memoization.
  - Replace setState-in-effect patterns (CallTimer, ChatImage,
    useChatSession, DashboardPage) with the React-recommended
    "adjust state during render" pattern.
  - Split SocketProvider.tsx into SocketProvider.tsx + SocketContext.ts
    so the file only exports components (fixes fast-refresh lint) and
    switch from a lazily-initialized ref to useState(() => ...) to
    avoid reading a ref during render.
  - Split Toast.tsx into Toast.tsx (trigger functions) +
    ToastVariants.tsx (components) for the same fast-refresh reason.
  - Move the emoji-picker anchor element into state, set via a ref
    callback, instead of reading emojiBtnRef.current during render.
  - Suppress react-hooks/refs on the two tanstack-virtual
    measureElement ref assignments, which are the library's documented
    API and not an unsafe ref read.
  - Fix two unsafe non-null-assertions on optional chains.
- Supply build-time env vars in the CI workflow and add a missing
  frontend/.env.example, since vite.config.ts validates required env
  vars at build time and there was no example file for the frontend.
@sudo-devKm sudo-devKm marked this pull request as ready for review July 5, 2026 13:41
@sudo-devKm sudo-devKm merged commit 2864a81 into main Jul 5, 2026
4 checks passed
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.

2 participants