fix(signals): account for queue burden in readiness score - #501
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 04eb8ee | Commit Preview URL Branch Preview URL |
Jun 10 2026, 07:16 AM |
github-actions
Bot
added
the
gittensor:bug
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
ghost
mentioned this pull request
JSONbored
force-pushed
the
codex/fix-quality-gate-undercounting-issue
branch
from
June 10, 2026 07:13
e43dacf to
4db067c
Compare
JSONbored
force-pushed
the
codex/fix-quality-gate-undercounting-issue
branch
from
June 10, 2026 07:15
4db067c to
04eb8ee
Compare
ghost
mentioned this pull request
JSONbored
added
the
gittensor:feature
This was referenced Jul 16, 2026
5 tasks
JSONbored
pushed a commit
that referenced
this pull request
Jul 17, 2026
…actor (#6769) self-review-context.js's LINKED_PR_PATTERN was a bare /PR|pull request #N/ with no closing-keyword requirement, despite claiming to mirror the host's extractLinkedPrNumbers exactly. The host requires close/fix/resolve precisely to avoid counting an incidental mention (its own #issue-body-pr-mention-pollution fix); the miner's copy never got it. So a body saying "similar to what we saw in PR #501" populated linkedPrs, the issue-quality report read the issue as "already references a PR", and the miner skipped an available issue. Mirror the host pattern and correct the comment. Closes #6769
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
signals.openPullRequests, which could produce a perfect queue score for small open-PR counts even whenQueueHealth.burdenScore/levelindicated critical burden from stale/unlinked/collision signals, allowing a readiness total to bypass a configured blocking quality Gate.Description
queuePressureScoreto acceptQueueHealthand use the more conservative score between open-PR pressure andQueueHealth.level, while preserving10/10for genuine zero open-PR evidence by short-circuiting onopenPullRequests === 0inqueuePressureScore.queuePressureOpenPullRequestScoreandqueuePressureLevelScorehelper functions and wire them intoqueuePressureComponentso level-derived burden cannot be ignored.test/unit/signals-coverage.test.tsthat constructs a small (4 PR) queue with stale/unlinked items and asserts the queue component scores low and reports the expected evidence.Testing
npm test -- test/unit/signals-coverage.test.ts, which passed after the changes.npm run typecheck, which passed with no errors.npm test, with all tests passing (1388 passed | 1 skipped).git diff --checkand code formatting/type checks with no issues reported.Codex Task