chore(governance): fill the template tokens that have a factual answer - #61
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 (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details🔇 Additional comments (2)
📝 SummarySummary by CodeRabbit
WalkthroughThe change replaces project-name and description placeholders with lucidscript-specific values in repository guidance, settings, and manifest files. ChangesProject metadata
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to This metadata-only change has no established runtime, tooling, or contract impact and is safe to merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the changes and identifies tokens that remain intentionally unresolved. However, it does not follow the repository template because it omits the required Summary, 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 project name 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.yml.github/CODE_OF_CONDUCT.md0-AI-MANIFEST.a2mlLeft 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}},{{CURRENT_YEAR}},{{PLACEHOLDER}},{{RESPONSE_TIME}}Filling those is a one-off decision about estate contact details, not a per-repo edit.