You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Draft pull requests are currently treated the same as normal OPEN pull requests in the mirror/scoring pipeline. This means work-in-progress drafts can be counted in open-PR paths even though they are not ready for review.
Why this is a problem
It creates a mismatch between contributor workflow (Draft = WIP) and scoring behavior.
Draft PRs can influence open-PR collateral/threshold logic before they are review-ready.
It allows low-signal draft activity to affect miner evaluation.
Summary
Draft pull requests are currently treated the same as normal
OPENpull requests in the mirror/scoring pipeline. This means work-in-progress drafts can be counted in open-PR paths even though they are not ready for review.Why this is a problem
Draft= WIP) and scoring behavior.Evidence
entrius/gittensorPR Fix: register issue no build artifact #271 is draft).statebut no draft flag:packages/das/src/entities/PullRequest.entity.tspackages/db/02_pull_requests.sqlstatebut notisDraft:packages/das/src/webhook/github-fetcher.service.tsstateonly;OPENgoes directly to open PR bucket:gittensor/validator/oss_contributions/mirror/load.pyReproduction
OPENPR (no draft distinction).Expected behavior
Draft PRs should be represented explicitly and either:
Suggested fix
is_draftfield in mirror DB/entity.isDraft(backfill/metadata paths)pull_request.draft(event path)gittensormirror load/scoring to apply intended policy for draft PRs.OPEN + isDraft=truevsOPEN + isDraft=false.