Repository navigation
feat: per-profile drafts dir (keep personal runs out of the public folder) - #42
Merged
Merged
Conversation
… public folder Adds optional brand.yaml output.drafts_dir. Omitted (demo + cron): drafts still go to the shared repo drafts/. Set to a relative path: drafts resolve against the profile's own folder, so a personal profile writes into its git-excluded directory and can never be committed to the public repo. resolveDraftsRoot() is unit-tested; _template documents the field. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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
Lets a profile decide where its drafts are written, so personal runs never land in the public
drafts/folder.brand.yamlfield:output.drafts_dir.drafts/.examples/, git-excluded) writes its drafts into its own directory, so they can never be committed to the public repo.resolveDraftsRoot()added tolib/emit.ts(pure, unit-tested: default / relative / absolute).run.ts(returns the raw spec) andcli.ts(resolves it)._template/brand.yamldocuments the field with a commented example.Why
Today the output path is hardcoded to
<repo>/drafts/. Any profile run writes there, including a personal one, which risks an accidental public commit (it happened, and had to be reverted). This makes the safe location automatic via config, matching the "brand.yaml is the single source of truth" rule.Test plan
resolveDraftsRootunit tests (default, relative-to-profile, absolute)sai-voice->drafts/, a profile withdrafts_dir: drafts-> its own folder🤖 Generated with Claude Code