Skip to content

chore: gitignore build-generated files#119

Merged
aspiers merged 3 commits intomainfrom
chore/gitignore-generated-files
Apr 12, 2026
Merged

chore: gitignore build-generated files#119
aspiers merged 3 commits intomainfrom
chore/gitignore-generated-files

Conversation

@aspiers
Copy link
Copy Markdown
Contributor

@aspiers aspiers commented Apr 12, 2026

Summary

  • Gitignore public/raw/, public/search-index.json, public/sitemap.xml, and lib/lastUpdated.json
  • Remove them from git tracking (files remain on disk, still generated at build time)

These files are regenerated by lib/generate-*.js scripts that run before next build in both npm run dev and npm run build. Since Vercel runs npm run build, they'll still be present in every deployment.

Why: public/raw/ is a byte-for-byte copy of pages/ — every markdown PR had doubled diffs and unnecessary merge conflict risk. The other three files are similarly regenerated from source on every build.

Test plan

  • Verify Vercel preview deployment serves /raw/*.md files correctly
  • Verify search works (search-index.json present in deployed output)
  • Verify sitemap.xml is accessible at /sitemap.xml
  • Verify pnpm dev locally still generates all files before starting the dev server

public/raw/, public/search-index.json, public/sitemap.xml, and
lib/lastUpdated.json are all regenerated by the lib/generate-*.js
scripts that run before `next build` in both the dev and build
npm scripts.

Tracking them in git caused noisy diffs on every PR that touched
markdown (the entire public/raw/ tree is a byte-for-byte copy of
pages/) and created unnecessary merge conflict risk.

Since Vercel runs `npm run build` which chains the generate scripts
before `next build --webpack`, these files will still be present in
the static export — they just won't be in the repo.
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 12, 2026

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

Project Deployment Actions Updated (UTC)
hypercerts-atproto-documentation Ready Ready Preview, Comment Apr 12, 2026 5:57pm
hypercerts-v0.2-documentation Ready Ready Preview, Comment Apr 12, 2026 5:57pm

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 12, 2026

Warning

Rate limit exceeded

@aspiers has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 19 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 15 minutes and 19 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 73009d4c-c10a-4a94-85ac-51524c236aec

📥 Commits

Reviewing files that changed from the base of the PR and between c0f1638 and 205b1e6.

📒 Files selected for processing (51)
  • .gitignore
  • lib/lastUpdated.json
  • public/raw/architecture/account-and-identity.md
  • public/raw/architecture/certified-group-service.md
  • public/raw/architecture/data-flow-and-lifecycle.md
  • public/raw/architecture/epds.md
  • public/raw/architecture/indexers-and-discovery.md
  • public/raw/architecture/overview.md
  • public/raw/architecture/portability-and-scaling.md
  • public/raw/core-concepts/cel-work-scopes.md
  • public/raw/core-concepts/certified-identity.md
  • public/raw/core-concepts/common-use-cases.md
  • public/raw/core-concepts/funding-and-value-flow.md
  • public/raw/core-concepts/hypercerts-core-data-model.md
  • public/raw/core-concepts/what-is-hypercerts.md
  • public/raw/core-concepts/why-at-protocol.md
  • public/raw/ecosystem/why-we-need-hypercerts.md
  • public/raw/getting-started/building-on-hypercerts.md
  • public/raw/getting-started/quickstart.md
  • public/raw/getting-started/testing-and-deployment.md
  • public/raw/getting-started/working-with-evaluations.md
  • public/raw/index.md
  • public/raw/lexicons/certified-lexicons.md
  • public/raw/lexicons/certified-lexicons/badge-award.md
  • public/raw/lexicons/certified-lexicons/badge-definition.md
  • public/raw/lexicons/certified-lexicons/badge-response.md
  • public/raw/lexicons/certified-lexicons/location.md
  • public/raw/lexicons/certified-lexicons/profile.md
  • public/raw/lexicons/certified-lexicons/shared-defs.md
  • public/raw/lexicons/hypercerts-lexicons.md
  • public/raw/lexicons/hypercerts-lexicons/acknowledgement.md
  • public/raw/lexicons/hypercerts-lexicons/activity-claim.md
  • public/raw/lexicons/hypercerts-lexicons/attachment.md
  • public/raw/lexicons/hypercerts-lexicons/collection.md
  • public/raw/lexicons/hypercerts-lexicons/contribution.md
  • public/raw/lexicons/hypercerts-lexicons/evaluation.md
  • public/raw/lexicons/hypercerts-lexicons/funding-receipt.md
  • public/raw/lexicons/hypercerts-lexicons/measurement.md
  • public/raw/lexicons/hypercerts-lexicons/rights.md
  • public/raw/lexicons/introduction-to-lexicons.md
  • public/raw/reference/certified-services.md
  • public/raw/reference/faq.md
  • public/raw/reference/glossary.md
  • public/raw/roadmap.md
  • public/raw/tools/hyperboards.md
  • public/raw/tools/hypercerts-cli.md
  • public/raw/tools/hyperindex.md
  • public/raw/tools/scaffold.md
  • public/search-index.json
  • public/sitemap.xml
  • vercel.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/gitignore-generated-files

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

The previous buildCommand ran next build directly, bypassing the
generate-*.js scripts that produce public/raw/, search-index.json,
sitemap.xml, and lastUpdated.json. This was fine when those files
were tracked in git, but now that they're gitignored the build
needs to generate them first.

npm run build already chains the generate scripts before next build.
@aspiers aspiers merged commit a78410d into main Apr 12, 2026
4 checks passed
@aspiers aspiers deleted the chore/gitignore-generated-files branch April 12, 2026 18:28
@aspiers
Copy link
Copy Markdown
Contributor Author

aspiers commented Apr 12, 2026

@s-adamantine Oops sorry meant to merge #118 not this one. But hopefully you are OK with it anyway! If not we can revert and discuss.

@aspiers
Copy link
Copy Markdown
Contributor Author

aspiers commented Apr 12, 2026

Oh. I merged #118 an hour ago and somehow forgot already?! This is why I shouldn't work on Sundays 😢

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