docs(agents): document Notra blog build workflow in AGENTS.md#117
Closed
tembo[bot] wants to merge 1 commit into
Closed
docs(agents): document Notra blog build workflow in AGENTS.md#117tembo[bot] wants to merge 1 commit into
tembo[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Requesting review from @leoisadev1 who has experience with the following files modified in this PR:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
|
Closing: documents the pre-SSR build-time blog, superseded by #120 (SSR-accurate). |
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
1 participant
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.
What
Adds a Docs and Blog section to
AGENTS.mddocumenting the Notra-powered blog build workflow that recent docs PRs (#110, #113, #116) introduced but that the agent instructions didn't yet cover.Why
PR #116 (merged) fixed an empty production blog by adding
NOTRA_API_KEYtopassThroughEnvinapps/fumadocs/turbo.json— turbo's strict env mode was stripping the var on Vercel. That gotcha, plus theposts:fetchcommand and theRefresh blog posts from Notraworkflow, are exactly the kind of repo-specific guidanceAGENTS.mdexists to capture.Changes
New section documents, all grounded in current repo usage:
apps/fumadocs; blog posts are fetched at build time byscripts/fetch-notra-posts.tsintosrc/lib/notra-posts.generated.ts.cd apps/fumadocs && bun run posts:fetch.NOTRA_API_KEYsetup (local.env.local/ Vercel env var) and the requirement to keep it inpassThroughEnvinapps/fumadocs/turbo.json.Refresh blog posts from Notraworkflow (.github/workflows/blog-schedule.yml) and its triggers.Existing sections were left untouched. Verified the referenced commands, files, env var, and workflow all exist in the repo.