Repository navigation
chore: add CI, contributor templates, and launch polish - #3
Conversation
- ci: add GitHub Actions workflow (pnpm 11 / Node 20) gating typecheck → lint → test → build on push to main and every PR - github: add PR template + bug/feature issue forms + config - docs: add project CLAUDE.md binding PR/issue authoring to the templates - env: document NEXT_PUBLIC_SITE_URL so OG/Twitter cards resolve on deploy - reward: set 50-star milestone to a free hosted version (landing + README) - readme: add CI status badge Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughAdds GitHub contributor infrastructure: a CI Actions workflow (typecheck, lint, test, build with pnpm), structured bug and feature request issue form templates, a populated PR template, a ChangesGitHub Contributor Infrastructure
Star Milestone Messaging and Env Config
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What & why
Adds the CI/CD and contributor fundamentals we were missing before launch, plus
two bits of launch polish.
.github/workflows/ci.ymlruns typecheck → lint → test → build onpush to
mainand every PR (pnpm 11 / Node 20,--frozen-lockfile,cancel-in-progress concurrency). README gets a matching CI status badge.
nudges contributors to the forms.
CLAUDE.mdbinds PR/issue authoring to thosetemplates and to passing all four gates before opening a PR.
NEXT_PUBLIC_SITE_URLdocumented in.env.exampleso Open Graph / Twittercard images resolve on a real deploy instead of
localhost.the
[your reward here]placeholder.How it was tested
pnpm test— 71 passedpnpm typecheckpnpm lintpnpm buildYAML for the workflow and issue forms was also validated with a parser.
Checklist
.envvalues committedScreenshots / notes
Follow-ups for the maintainer:
.github/ISSUE_TEMPLATE/config.ymlshould point at issues instead.Summary by CodeRabbit
New Features
Documentation
Chores