chore(governance): fill the template tokens that have a factual answer - #57
Conversation
…swer These files shipped as the raw template, tokens and all. The tokens that name a fact the repository itself answers - project name, owner, forge, description - are filled here. The tokens that name a decision (contact addresses, PGP key, response time) are left exactly as they are and listed in the PR.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (21)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe repository settings template now uses a fixed description. Its comment explains totality discipline instead of placeholder replacement. ChangesRepository settings
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the main change and identifies intentionally unchanged tokens. It does not follow the required template structure and omits the Changes, RSR Quality Checklist, Testing, and Screenshots sections.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the settings bright Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
1 participant
The template tokens in these files had a factual answer, so they are filled:
.github/settings.ymlLeft deliberately for the owner — these ask for values a machine must not invent (a wrong security contact is worse than an obviously-unfilled one):
.github/CODE_OF_CONDUCT.md:{{CONDUCT_EMAIL}},{{CONDUCT_TEAM}},{{PLACEHOLDER}},{{RESPONSE_TIME}}Filling those is a one-off decision about estate contact details, not a per-repo edit.