-
-
Notifications
You must be signed in to change notification settings - Fork 90
chore: fix gittensory -> loopover rename residue #6074
Copy link
Copy link
Closed
Labels
maintainer-onlyOwner-only work — yields no Gittensor points.Owner-only work — yields no Gittensor points.orbGittensory Orb related - maintainer self-hosting analytics.Gittensory Orb related - maintainer self-hosting analytics.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Description
Metadata
Metadata
Assignees
Labels
maintainer-onlyOwner-only work — yields no Gittensor points.Owner-only work — yields no Gittensor points.orbGittensory Orb related - maintainer self-hosting analytics.Gittensory Orb related - maintainer self-hosting analytics.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Part of #6065. Small, mechanical, low-risk.
Problem
Found while auditing the review-comment stack:
<!-- gittensory-pr-panel:v1 -->(packages/loopover-engine/src/signals/engine.ts ~4543).gittensory.ymlwhen the actual files in that directory areloopover.full.ymletc.Proposed fix
src/github/comments.ts'smarkerAliases()matches multiple marker strings for backward compatibility with in-flight comments across the rename; confirm whether adding a new alias (rather than a straight rename) is needed so in-flight PR comments using the old marker aren't orphaned, before changing the constant.Files