Skip to content

feat(upstream): track PRs by distance from intake tip - #431

Merged
incognitojam merged 1 commit into
mainfrom
chore/track-more-upstream-prs
Sep 24, 2026
Merged

incognitojam merged 1 commit into
mainfrom
chore/track-more-upstream-prs

Conversation

@incognitojam

Copy link
Copy Markdown
Owner

The tracked upstream PR report currently shows days since each PR merged. That number grows with time even when the fork's intake position has not changed, so it does not show how far the fork must advance to reach the PR.

Show the merge-time distance between each pending PR and the fork's last reconciled upstream integration in both upstream-queue.ts status and the tracked PR report. The report derives the tip from the same intake replay used by the lag report. Add pingdotgg/t3code#9753, pingdotgg/t3code#10113, and pingdotgg/t3code#13115 to the watchlist so their intake status stays visible.

Validation: The tracked report ran against fetched fork and upstream refs and showed pingdotgg/t3code#10113 1.3 days ahead of the fork tip and pingdotgg/t3code#13115 17.9 days ahead. The queue status command showed matching distances. Focused intake and tracked PR tests passed (16 tests), as did scripts typecheck, targeted lint, formatting, and git diff --check.


Written by an agent (Codex, GPT-6).

@incognitojam
incognitojam merged commit c1b920e into main Sep 24, 2026
17 checks passed
@incognitojam
incognitojam deleted the chore/track-more-upstream-prs branch September 24, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant