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>
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'.
#93) * feat(dashboard): add slim issues endpoint to replace per-miner fan-out New DashboardModule exposing GET /api/v1/dashboard/issues?since= for the gittensor-ui dashboard's trend chart and Issues Solved KPI. Returns slim issue rows (one bulk call) so the UI no longer fans out N parallel /miners/<id>/issues requests on every dashboard mount. The mirror is roster-blind by design: every issue is returned regardless of author. The UI blends with the gittensor miner roster client-side to filter to subnet authors. Validator-facing /miners/<id>/issues is unchanged. * style(api.module): prettier formatting --------- Co-authored-by: anderdc <me@alexanderdc.com>
# Conflicts: # packages/das/src/webhook/github-fetcher.service.ts # packages/das/src/webhook/handlers/issue.handler.ts # packages/das/src/webhook/handlers/label.handler.ts
Add GET /api/v1/repos/:owner/:repo/maintainers, returning users whose latest known association for the repo is OWNER, MEMBER, or COLLABORATOR. Reads the existing contributor_repo_roles view — no new table or GitHub API permission. An unknown repo returns an empty maintainers list. Consumed by the gittensor validator to route the per-repo maintainer_cut emission carve-out. Co-authored-by: anderdc <me@alexanderdc.com>
Collaborator
Author
|
Closing — das-github-mirror is adopting gittensor's promotion model: |
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
8 participants
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.
Promotes
testtomain.Net change
The only content difference between
mainandtestis the repo maintainers endpoint (#104):GET /api/v1/repos/:owner/:repo/maintainers(ReposController/ReposService).OWNER,MEMBER, orCOLLABORATOR, read from the existingcontributor_repo_rolesview.Schema / runbook
No schema changes. The endpoint reads the existing
contributor_repo_rolesview — no new table, no migration, no runbook SQL required for this deploy.