Repository navigation
feat: link an existing repository to a request claim - #33
Merged
Merged
Conversation
- POST /api/requests/:id/repo records a repository the claimer maintains (same maintain/admin check as submitting a plugin); null unlinks it. Emits the new request.repo_linked webhook event. - GET /api/submit/owners lists the GitHub account and its organizations, the valid owners for a scaffolded repository. - Both are exposed over MCP (linkRequestRepo, listRepoOwners). - The scaffold dialog gains a "link an existing one" mode and an organization select.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
This branch was successfully deployed
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
1 participant
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.
What
Claimers can now attach a repository they already maintain to their claim, instead of only scaffolding a new one, and pick the scaffold organization from a list.
POST /api/requests/:id/repo(linkRequestRepo): body{ repoUrl, returnTo? }. Requires a claim on an approved request and maintain/admin on the repository through a linked identity, the same check as submitting a plugin (checkOwnership).repoUrl: nullunlinks. Emits the newrequest.repo_linkedwebhook event.GET /api/submit/owners(listRepoOwners): the GitHub account first, then its organizations (/user/orgs, covered by theread:orgscope already requested at sign-in).linkRequestRepounderrequests:write,listRepoOwnersunderaccount:read.Tests
tests/routes/request-repo.test.ts: claim required, link with maintain, refusal without it, unknown host, unlink, owners ordering.bun test: 640 pass.svelte-checkand biome clean.Not included
packages/tabularium-rs/openapi.jsonis not regenerated.