chore(governance): fill the template tokens that have a factual answer - #58
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. (14)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe repository settings replace the description template with the concrete AffineScript project description. The related header comment now states the final description. ChangesRepository description
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 settings change and identifies the deliberately unchanged tokens. It does not follow the required template and omits the 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 sees the template fade Comment |
|
🔍 Hypatia Security ScanFindings: 70 issues detected
View findings[
{
"reason": "Job `triage` in label-triage.yml has no `timeout-minutes:` declaration. Default is 6 hours — a stuck codeload fetch or runner hang can burn budget. Add `timeout-minutes: 10` (or proportional).",
"type": "missing_timeout_minutes",
"file": "label-triage.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium",
"recipe_id": "recipe-add-workflow-timeout-minutes",
"job": "triage"
},
{
"reason": "Job `sync` in labels.yml has no `timeout-minutes:` declaration. Default is 6 hours — a stuck codeload fetch or runner hang can burn budget. Add `timeout-minutes: 10` (or proportional).",
"type": "missing_timeout_minutes",
"file": "labels.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium",
"recipe_id": "recipe-add-workflow-timeout-minutes",
"job": "sync"
},
{
"line": 44,
"reason": "job in .github/workflows/push-email-notify.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/push-email-notify.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 24,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 44,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 64,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 84,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 104,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 124,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
},
{
"line": 156,
"reason": "job in .github/workflows/mirror.yml references `secrets.*` but does not install `step-security/harden-runner` — review outbound-egress monitoring",
"type": "RE001",
"file": ".github/workflows/mirror.yml",
"action": "report",
"rule_module": "research_extensions",
"severity": "warn"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |



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_TEAM}},{{PLACEHOLDER}},{{RESPONSE_TIME}}Filling those is a one-off decision about estate contact details, not a per-repo edit.