chore: remove dead OutBot and HuskyCat configs#163
Conversation
Greptile SummaryThis PR removes two stale root-level config files —
Confidence Score: 5/5Safe to merge — both files are confirmed dead with no CI backing and no downstream references. Pure deletion of two config files that are unreferenced by any workflow. No logic changes, no regressions possible. The only follow-up (cleaning up the FORGEJO_TOKEN secret) is outside the codebase and non-blocking. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR / Issue Event] -->|"was intended to trigger"| B[HuskyCat]
B -->|"auto-label via rules"| C[GitHub Labels]
B -->|"triage sync"| D[Codeberg Labels]
B -.->|"no CI workflow ever ran this"| X((Dead))
E[main branch push] -->|"was intended to trigger"| F[OutBot]
F -->|"git mirror"| G[Codeberg Repo]
F -.->|"no automated trigger — ran once manually 2026-02-23"| Y((Dead))
X -->|removed in this PR| H[.huskycat.yaml deleted]
Y -->|removed in this PR| I[.outbot.yml deleted]
style X fill:#ff6b6b,color:#fff
style Y fill:#ff6b6b,color:#fff
style H fill:#51cf66,color:#fff
style I fill:#51cf66,color:#fff
Reviews (1): Last reviewed commit: "chore: remove dead HuskyCat config" | Re-trigger Greptile |
OutBot sync to Codeberg ran once (2026-02-23) and was never automated. HuskyCat labeling has no CI backing. Removing stale configs.