-
-
Notifications
You must be signed in to change notification settings - Fork 77
feat(github-app): merge-readiness aggregate gate #551
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Milestone
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Parent roadmap: #525
Parent phase: #528
Background
A repo can enable up to four separate gates (linked-issue, duplicate, quality, and soon slop). Maintainers want ONE required check for branch protection, not four.
Goal
A tunable
mergeReadinessGateModecomposite gate that rolls linked-issue + duplicate + readiness + slop into a single pass/fail with a "what's still blocking" summary.Current Behavior
evaluateGateCheck(src/rules/advisory.ts:139) already aggregates blocker classes but isn't exposed as a single configurable composite.Desired Behavior
mergeReadinessGateMode(off/advisory/block) toRepositorySettings; when enabled, theGittensory Gateconclusion reflects the composite and the summary lists each unmet condition.buildPublicReadinessScore+ the existing blocker classes.Implementation Requirements
gateCheckPolicy(processors.ts:760). KeepGittensory Gatethe single required check.Public/Private Output Boundaries
sanitizeForCheckRun; no private scores.Acceptance Criteria
Testing Requirements
npm run test:ci, 97%+ coverage. Composite on/off/advisory/block tests.