feat(signals): multiplier-aware opportunity ranking + maintainer-intent issue quality (#699, closes #186) - #706
Conversation
…nt issue quality (#699, closes #186) Issue-watch path A: enrich cross-repo contributor opportunities so miners can grab the highest-value issues first, and stop steering them at a maintainer's own work. - ContributorOpportunity gains `multiplierTier` (maintainer_created | community) and `availability` (ready | maintainer_wip). Maintainer-CREATED grabbable issues carry the biggest Gittensor reward multiplier, so they get a score boost + a "highest contribution multiplier" reason and rank above equivalent community issues; a maintainer's own WIP/internal-labelled issue is heavily penalised, forced to `hold`, and flagged not-recommended. - buildIssueQualityReport now reads authorAssociation (#186): every maintainer-authored issue gets a confirm-scope warning, and maintainer-WIP issues can never read "ready" (downgraded to needs_proof). A clean maintainer-created issue still reads ready — it's the prime target. - New MAINTAINER_WIP_LABELS + isMaintainerWipIssue() helper shared by both. - OpenAPI ContributorOpportunity schema extended with the two new enums. - Tests: ranking (maintainer-created > community > WIP) and the #186 confirm-warning / never-ready-WIP invariants.
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
ghost
added
the
|
gittensory · advisory review Reviewed 6 changed file(s) — two independent AI reviewers. Suggested action: 🔍 Manual review. The changed route's preview could not be captured — review the rendered page manually before merging. Reviewer A · Suggestions
Worth double-checking
Reviewer B · Suggestions
Worth double-checking
Warning Could not capture a preview of the changed route(s) — review the rendered page manually before merging. Before = production · After = this PR's preview deploy.
|
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 0a1e2da | Commit Preview URL Branch Preview URL |
Jun 14 2026, 09:59 AM |
…sues (#699 path B) (#735) Miners subscribe to repos for NEW grabbable, high-multiplier issues; when one opens, the watchers are notified through the #535 pipeline. Completes the active half of #699 (path A shipped the pull surface in #706). - issue_watch_subscriptions table (migration 0036) + repositories CRUD (upsert idempotent on login+repo, list-for-login, delete, list-watchers-for-repo); labels lowercased for case-insensitive filtering. - engine: export isGrabbableHighMultiplierIssue (open + maintainer-created + not WIP) — the exact condition path A ranks up. - notifications/service: detectIssueWatchEvents fans out one event per matching watcher (label filter; skips the issue's own author), DB-backed so it sits alongside the pure detectNotificationEvents; buildIssueWatchNotification (public-safe "open to grab" copy). New eventType issue_watch_match (its pullNumber field carries the issue number). - processors: the issue-opened webhook path detects watch events and fans them into the existing notify-evaluate enqueue loop. - MCP gittensory_watch_issues (watch/unwatch/list, self-scoped) — the miner surface; matches surface through gittensory_list_notifications. Tests: grabbable-issue logic, subscription CRUD, fan-out detection (label filter / author-skip / no-author edge), public-safe copy, the dispatch, the MCP tool (incl. self-scope), and the webhook end-to-end. 97% coverage held.
1 participant
What
Issue-watch path A (slice of #699) + the #186 fix, in one PR because both hinge on reading an issue's author association + labels to classify its reward-multiplier tier and whether it's a real outside-contributor target.
Multiplier-aware opportunity ranking (#699)
ContributorOpportunitynow carries:multiplierTier:maintainer_created|community— maintainer-CREATED issues typically carry the biggest Gittensor reward multiplier, so a miner should grab them before anyone else.availability:ready|maintainer_wip— a maintainer's own in-progress/internal-labelled issue is not an open target.Ranking behaviour in
buildContributorOpportunities:+12score boost, a "highest contribution multiplier" reason, and a confirm-scope warning. It now outranks an equivalent community issue with the same labels/lane.-45penalty, forcedfit: "hold", and a "not a recommended outside-contributor target" warning.Maintainer-intent issue quality (closes #186)
buildIssueQualityReportpreviously ignoredauthorAssociation, so a maintainer-authored issue could silently read "ready". Now:ready(downgraded toneeds_proof).ready— it's the prime high-multiplier target, just flagged to confirm intent.Shared
MAINTAINER_WIP_LABELS+isMaintainerWipIssue()helper back both paths; OpenAPIContributorOpportunityschema extended with the two new enums.Why
Miners need to spot and grab maintainer-created issues early (biggest multiplier) without being steered onto a maintainer's own active work. This is the deterministic, gittensor-native signal a miner's harness can't compute itself — it flows through the existing decision-pack +
gittensory_get_decision_packMCP surface automatically.Tests
signals.test.ts: maintainer-created > community > WIP ranking, tier/availability, reasons/warnings, forcedhold.issue-quality.test.ts: confirm-warning on maintainer-authored; maintainer-WIP neverready.Advances #699 (path A: the pull surface). Delivery (
gittensory_watch_issues+ push via #535) remains for the rest of #699.