Description
GET/POST /api/v1/miners/:githubId/pulls always sorts results by p.created_at DESC. For MERGED and CLOSED PRs that enter the scoring window via merged_at / closed_at, this ranks recently merged/closed work below older OPEN PRs and makes validator responses look stale.
Steps to Reproduce
- Mirror two PRs by the same miner in the same repo:
- PR A:
OPEN, created_at = 2 days ago
- PR B:
CLOSED, created_at = 60 days ago, closed_at = 1 day ago
- Call
GET /api/v1/miners/{id}/pulls?since= (30 days ago).
- PR A appears before PR B even though B closed more recently.
Expected Behavior
Sort by the timestamp relevant to each state: created_at for OPEN, merged_at for MERGED, closed_at for CLOSED.
Actual Behavior
ORDER BY p.created_at DESC
Environment
- OS: Linux
- Runtime/Node version: Node 20
Description
GET/POST /api/v1/miners/:githubId/pullsalways sorts results byp.created_at DESC. ForMERGEDandCLOSEDPRs that enter the scoring window viamerged_at/closed_at, this ranks recently merged/closed work below older OPEN PRs and makes validator responses look stale.Steps to Reproduce
OPEN,created_at= 2 days agoCLOSED,created_at= 60 days ago,closed_at= 1 day agoGET /api/v1/miners/{id}/pulls?since=(30 days ago).Expected Behavior
Sort by the timestamp relevant to each state:
created_atfor OPEN,merged_atfor MERGED,closed_atfor CLOSED.Actual Behavior
Environment