feat: add Commit+ page - #31
Open
hohops wants to merge 7 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hohops
force-pushed
the
feat/fetch-contributors-from-github
branch
from
July 31, 2026 21:46
a28fe0e to
926a8f4
Compare
hohops
changed the title
Local and CI environments could drift freely: no engines field, no .nvmrc, and CI hardcoded Node 22 while development happened on Node 24. - pin Node to 24.x via .nvmrc + engines (yarn 1 enforces this on every script, so a wrong runtime now fails loudly instead of silently) - CI reads .nvmrc via node-version-file so there is a single source of truth instead of two that can diverge - declare packageManager for corepack - drop TypeScript 6.0.3, which is far outside the >=4.7.4 <5.6.0 window supported by @typescript-eslint 7; pin 5.9.3 exactly so the declared range matches what actually resolves Verified on Node 24.15.0: install --frozen-lockfile, typecheck, lint and build all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A merge that mixes two lockfiles produces a file that parses but no longer describes a real dependency tree. merge=binary makes git conflict instead, forcing the resolution to be an explicit yarn install. linguist-generated keeps lockfile churn collapsed in GitHub diffs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Resolve the yarn.lock conflict in favour of this branch. master's lockfile (28e3571) is a stale copy from the 50e7b54 era: 761 lines, the old yarnpkg registry, and missing @commitpt/design-system, typescript, eslint, prettier, husky and sharp. It landed in a commit made 90 seconds after a clean fast-forward pull, so nothing was ever actually merged — an old working-tree file was committed over a correct one. Taking this branch's lockfile restores the full tree. Because the merge is recorded here, merging back into master now carries the correct file instead of silently keeping the broken one. Verified: install --frozen-lockfile, typecheck and lint all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Replace lorem ipsum throughout with actual Portuguese copy describing the premium tier. Extract FAQ items into shared data module and reuse existing questions.
- Replace em dashes with hyphens/commas in Commit+ page and FAQ - Change '+' symbol color from green to cyan - Replace diff metaphor with terminal git workflow session - Add syntax highlighting for git commands
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new Commit+ page following the existing design system.
app/commit-plus/page.tsx:FeatureCard)FaqAccordionclient wrapper component/commit-plusto the sitemap