ci(labels): apply namespaced gittensor reward labels

[JSONbored]

Summary

• update the type-label workflow to apply namespaced Gittensor reward labels
• require feature PRs to close a feature issue before receiving gittensor:feature
• keep gittensor:priority manual-only while preventing auto-label churn when it is present

What changed

• scripts/github-type-label.mjs now applies gittensor:bug and gittensor:feature instead of plain bug and feature.
• Feature PR auto-labeling checks closing issue references and only labels when a referenced issue is a feature issue.
• The workflow self-creates the two auto labels if they are missing, while gittensor:priority remains manual.
• Unit coverage now includes namespaced labels, feature-issue gating, referenced issue fetches, and missing-label creation.

Why

The Gittensor registry config now uses explicit gittensor:* labels with a zero default multiplier. CI should support that policy without turning every normal feature label into a scoring label.

Validation

• npx vitest run test/unit/github-type-label.test.ts
• git diff --check
• npm run actionlint
• npm run typecheck

Notes

• Repository labels gittensor:bug, gittensor:feature, and gittensor:priority were created in GitHub so the workflow and manual priority flow are ready.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	dfd20af	Commit Preview URL Branch Preview URL	Jun 05 2026, 08:11 PM

[gittensory]

Important

Gittensory found maintainer review notes

Public GitHub metadata was checked for review readiness. Gittensor-specific context appears only when confirmed.

Readiness score: 86/100

Signal	Result	Evidence	Action
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.	Explain no-issue PR.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.	No action.
Review load	✅ 20/20	Readiness component derived from cached public PR metadata and labels; size label size:L.	No action.
Validation evidence	✅ 25/25	PR body includes validation/test evidence.	No action.
Open PR queue	❌ 3/10	32 open PR(s), 20 likely reviewable.	Expect slower review.
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; official public miner data; 316 PR(s), 630 issue(s).	No action.
Gate result	✅ Passing	No configured blocker found.	No action.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Review load = cached public PR metadata such as size labels, changed paths, and preflight status.
• Open PR queue = repo-wide review pressure; it is not a PR quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, Kotlin, MDX, Shell
• Official Gittensor activity: 316 PR(s), 630 issue(s).
• PR-specific overlap: none found.

Maintainer notes

• No linked issue detected: The planned PR does not reference a closing issue or explicit linked issue number.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Expect slower review.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. Learn more about Gittensor contribution workflows.