chore: ignore marketing build output and the whole scripts/ working area - #87
Merged
bladehell-ai merged 1 commit intoAug 21, 2026
Merged
Conversation
Two changes to .gitignore. **marketing/** gained the same build-output block every other app already has. `marketing/tsconfig.tsbuildinfo` — a 98KB incremental TypeScript artifact — had been sitting untracked in the working tree; `.vercel` is included because the marketing site deploys from there and the directory holds project linkage, not source. **scripts/** is broadened from the `prod-*` prefix (added in #84) to the whole directory. The prefix only caught files someone remembered to name correctly. A directory-wide rule inverts the default: a new script is out unless it is added deliberately with `git add -f`, which is the right way round for a folder whose contents are one-off work against live production data. Already-tracked scripts are unaffected — an ignore rule never untracks a file — so scripts/deploy.sh and scripts/scan-for-malware.sh stay in the repo exactly as they are. Verified with `git check-ignore`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
bladehell-ai
deleted the
chore/ignore-marketing-build-output-and-scripts
branch
August 21, 2026 13:58
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
Two
.gitignorechanges, on top of #84.marketing/gets the build-output block every other app already has:marketing/tsconfig.tsbuildinfo— a 98KB incremental TypeScript artifact — had been sitting untracked in the working tree..vercelis in there because the marketing site deploys from it and the directory holds project linkage, not source.scripts/is broadened from theprod-*prefix that #84 added to the whole directory:Why the broader rule
The
prod-*prefix only caught files someone remembered to name correctly. A directory-wide rule inverts the default: a new script is out unless it is added deliberately withgit add -f scripts/<name>. For a folder whose contents are one-off work against live production data, that is the right way round.What does not change
Already-tracked scripts are unaffected — an ignore rule never untracks a file. Verified with
git check-ignore:scripts/deploy.shscripts/scan-for-malware.shscripts/prod-set-checkin.shscripts/some-new-tool.shmarketing/tsconfig.tsbuildinfo*.tsbuildinfofrom #84 is preserved.Note
scripts/prod-fix-overnight-checkout-data.sqlandscripts/prod-move-six-to-evening.sqlare already tracked and therefore stay in the repo despite this rule. Untracking them needs an explicitgit rm --cached; left out of this PR deliberately, since it deletes committed files.Risk
None. Ignore-rule-only change; no tracked file is added, removed or modified.
🤖 Generated with Claude Code