fix(deployment): only block files with explicit confidential markers, not filename patterns
- Removed filename pattern checks (session-handoff, draft, etc.) - Now only blocks files with content markers: [INTERNAL], [CONFIDENTIAL], [DO NOT PUBLISH] - Allows session handoff and internal documentation in docs/ directory - Still blocks actual credentials and sensitive content Rationale: Filename patterns were too broad and blocked legitimate internal documentation. Session handoffs are fine in docs/ as long as they don't contain actual sensitive data. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
3aae86edf9
commit
8021197bf0
1 changed files with 7 additions and 9 deletions
|
|
@ -82,13 +82,11 @@ function scanFile(filePath) {
|
||||||
return null;
|
return null;
|
||||||
}
|
}
|
||||||
|
|
||||||
// Check filename
|
// ONLY check content markers, not filename patterns
|
||||||
const pathCheck = checkFilePath(filePath);
|
// Rationale: Session handoffs and internal docs are fine in docs/ directory
|
||||||
if (pathCheck.confidential) {
|
// as long as they don't contain actual sensitive content (credentials, etc.)
|
||||||
return { file: filePath, ...pathCheck };
|
// Filename patterns are too broad and catch legitimate internal documentation
|
||||||
}
|
|
||||||
|
|
||||||
// Check content
|
|
||||||
const contentCheck = checkFileContent(filePath);
|
const contentCheck = checkFileContent(filePath);
|
||||||
if (contentCheck.confidential) {
|
if (contentCheck.confidential) {
|
||||||
return { file: filePath, ...contentCheck };
|
return { file: filePath, ...contentCheck };
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue