|
37 | 37 | duplicates: block # block | advisory | off — block obvious duplicate PRs |
38 | 38 | readiness: |
39 | 39 | mode: advisory # advisory | off — readiness score is informational and never blocks the Gate |
40 | | - minScore: 60 |
| 40 | + minScore: 40 # lowered from 60: 73% false-positive rate showed PRs scoring 40-59 merge freely |
41 | 41 | # aiReview: # opt-in AI maintainer review (off by default; needs the AI flags enabled) |
42 | 42 | # mode: advisory # block | advisory | off — block only blocks on a dual-model consensus defect |
43 | 43 | # byok: false # use a maintainer Anthropic/OpenAI key for the write-up; consensus stays on the free/default reviewer |
|
55 | 55 | # relatedWork: false # linkedIssue | relatedWork | reviewLoad (Change scope) | |
56 | 56 | # openPrQueue: false # validationEvidence (Validation posture) | openPrQueue (Contributor workload) | contributorContext | gateResult |
57 | 57 |
|
| 58 | +# Linked-issue label propagation (#priority-linked-issue-gate, #priority-linked-issue-gate-ownership): a PR |
| 59 | +# that closes/fixes/resolves an issue inherits that issue's point-bearing gittensor:* label onto the PR |
| 60 | +# itself, instead of the PR's own label being decided purely by its commit-title prefix. bug/feature are |
| 61 | +# `trustMaintainerAuthoredIssue: true` (routine categorization, no reward at stake, and the title-based |
| 62 | +# fallback already has zero equivalent verification) so they propagate even when the PR author isn't a |
| 63 | +# formal GitHub assignee of the issue — our issues are almost always maintainer-authored for open pickup and |
| 64 | +# rarely formally assigned. priority intentionally omits the flag: it is the scarce, maintainer-hand-picked |
| 65 | +# reward label, and must still require the PR author to be the issue's actual author/assignee. |
| 66 | +# |
| 67 | +# Review-evasion protection: closing or converting-to-draft your OWN PR while gittensory has an active |
| 68 | +# review pass running, a prior recorded gate failure, or a repeated ready<->draft cycle on this PR, is |
| 69 | +# treated as dodging the one-shot review rather than an ordinary action (layered OVER the dashboard's |
| 70 | +# own default of "off"). |
| 71 | +settings: |
| 72 | + linkedIssueLabelPropagation: |
| 73 | + enabled: true |
| 74 | + mode: exclusive_type_label |
| 75 | + mappings: |
| 76 | + - issueLabel: "gittensor:bug" |
| 77 | + prLabel: "gittensor:bug" |
| 78 | + removeOtherTypeLabels: true |
| 79 | + trustMaintainerAuthoredIssue: true |
| 80 | + - issueLabel: "gittensor:feature" |
| 81 | + prLabel: "gittensor:feature" |
| 82 | + removeOtherTypeLabels: true |
| 83 | + trustMaintainerAuthoredIssue: true |
| 84 | + - issueLabel: "gittensor:priority" |
| 85 | + prLabel: "gittensor:priority" |
| 86 | + removeOtherTypeLabels: true |
| 87 | + reviewEvasionProtection: close |
| 88 | + |
58 | 89 | # Repo-doc generation roadmap (#2993/#3002) — opt-in only, off by default. Uncomment to let Gittensory open a |
59 | 90 | # PR generating AGENTS.md/CLAUDE.md from this repo's own profile. |
60 | 91 | # repoDocGeneration: |
|
0 commit comments