chore(ci): remove the rhodibot rule that could never delete anything - #7
Conversation
The rule deletes ../../../../.github/CONTRIBUTING.md when a nested CONTRIBUTING.md is present. These workflows run from the repository root, so that path resolves outside the repository - the condition is never true and the file is never touched. It has been inert since it was written. Removed, along with the stale mention in each file's header comment. - `actions/validate/.github/workflows/rhodibot.yml` - `bindings/deno/.github/workflows/rhodibot.yml` - `bindings/haskell/.github/workflows/rhodibot.yml` - `bindings/rust/.github/workflows/rhodibot.yml` - `editors/vscode/.github/workflows/rhodibot.yml`
This copy spells the path ../../../ rather than ../../../../ (pandoc sits one level deep, not two), which is still outside the repository when the workflow runs from the root - so it is equally inert.
|
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 (6)
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. (7)
🔇 Additional comments (6)
📝 SummarySummary by CodeRabbit
WalkthroughThe Rhodibot workflows no longer delete duplicate parent-directory ChangesRhodibot rule update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 workflow trail Comment |
|
…low (#9) #7 removed the dead `CONTRIBUTING` delete rule from five of the six nested rhodibot workflows, but in `editors/vscode/…` it changed only the header comment — the rule itself is still there: ```sh if [ -f "editors/vscode/.github/CONTRIBUTING.md" ] && [ -f ".github/CONTRIBUTING.md" ]; then rm editors/vscode/.github/CONTRIBUTING.md ``` `editors/vscode/.github/CONTRIBUTING.md` **exists on `main`** — it is a deliberate nested guide, not a duplicate. Nothing is at risk today (GitHub reads workflows only at the repository root, and this one is nested), but a rule that deletes a real file is not something to leave lying about for whoever moves this workflow up later. This is the same removal #7 made in the other five files, applied to the sixth.



rhodibot.ymlcarries a rule that deletes a duplicate guide:It can never fire. These workflows run from the repository root, where
../../../../resolves outside the repository — so the second condition is never true and the file is never a candidate. The rule has been inert the whole time.That mattered when the guide moved to
.github/CONTRIBUTING.md(#5): the obvious reading of this rule is "something will delete that file", and it will not. Removing it so the workflow says what it does.Six copies, one per nested sub-project (
actions/validate,bindings/{deno,haskell,rust},editors/vscode,pandoc) — the stale mention in each file's header comment goes with it.No behaviour change: the condition was already false on every run.