Repository navigation
chore: inherit the default community health files - #26
Conversation
Remove the repository's own security policy, code of conduct and pull request template so GitHub applies the account-wide defaults from the finallyjay/.github repository: one template for every repo, maintained in one place. Links that pointed at the removed files now point at the repository's security policy page and the shared code of conduct, and the issue chooser's security link uses private vulnerability reporting. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QaN67cqjmynmoHj6hJs9TP
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Disabled knowledge base sources:
📝 SummarySummary by CodeRabbit
WalkthroughThe pull request removes the local pull request template, Code of Conduct, and security policy. It updates ChangesGovernance documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Why
Every finallyjay repository should present the same security policy, code of conduct and pull request template. GitHub already applies the files in finallyjay/.github to any repository — public or private — that does not ship its own copy, so per-repo copies only create drift.
What
…/security/policyand the shared code of conduct..github/ISSUE_TEMPLATE/config.yml: the security link uses GitHub private vulnerability reporting; Discussions links (feature disabled) are dropped where present.Repository-specific issue forms and
CONTRIBUTING.mdare kept; they hold project-specific content.🤖 Generated with Claude Code
https://claude.ai/code/session_01QaN67cqjmynmoHj6hJs9TP