Conversation
When `since` is provided, behavior is unchanged: OPEN created on/after, CLOSED closed on/after — the scoring window. When `since` is omitted, the response now returns all currently-OPEN issues with no time bound and no CLOSED history. Callers asking for "current open-issue load" no longer need a synthetic epoch-since workaround that pulls a full all-time payload. Lets the validator's open-issue spam-multiplier count old still-open issues that fall outside the scoring lookback window — the gap called out in entrius/gittensor#929 / PR #930. Co-authored-by: anderdc <me@alexanderdc.com>
* Fix stale PR file fetch completion * Fix stale PR file write race * Run tests before DAS build * Drop contributor test artifacts * Slim stale PR file completion fix --------- Co-authored-by: mkdev11 <MkDev11@users.noreply.github.com>
* Fix label actor role evidence * Run tests before DAS build * Drop contributor DB view tests --------- Co-authored-by: mkdev11 <MkDev11@users.noreply.github.com>
* Fetch base content for deleted PR files * Tighten deleted file content regression * Strengthen deleted file content coverage * Drop contributor fetcher test --------- Co-authored-by: mkdev11 <MkDev11@users.noreply.github.com>
2 tasks
Branch protection on main requires a 'pr-source-check' status, but no workflow was publishing it — leaving PRs into main perma-blocked. Mirror the workflow used in entrius/gittensor and entrius/gittensor-ui: enforce that PRs into main originate from 'test'.
LandynDev
approved these changes
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes 7 commits from
testtomain:Prod schema migration (runbook)
packages/db/is only applied to fresh volumes, so prod needs the following SQL applied manually after merge. Both changes are idempotent on a clean prod (no existing constraint, no schema drift on the view).From #8 —
pull_requestsgains a CHECK that MERGED rows have amerged_at. If any prod row violates it, backfill before adding (or useNOT VALID+VALIDATE CONSTRAINTafter backfill).From #14 —
contributor_repo_rolesview now unions reviews and comments alongside PRs/issues, and orders byobserved_at, source_rank, source_keyso reviewer/commenter associations contribute to the latest known role.24_view_pr_labels_by_actor.sqlchanged in #14 but only in comments — no DDL to apply.Test plan
\d pull_requestsshowspull_requests_merged_has_merged_atcontributor_repo_rolesreturns rows for a known reviewer-only or commenter-only contributor