hetaoBackend / hetaoBackend/mcode-passport
Validate GitHub Copilot subscription with a real-account E2E
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Goal
Promote the GitHub Copilot subscription connector from experimental to compatible only after a real Copilot-enabled account passes the full local-gateway path.
Required evidence
- device OAuth login and persisted credential
- forced expiry followed by successful Copilot token refresh
- availableModelIds filtering and credential-specific base URL
- text SSE through MiniMax Code compatible endpoint
- tool call SSE through the same endpoint
- auth, quota, and upstream error mapping
- current GitHub plan/policy review for third-party local clients
A normal GitHub token without Copilot entitlement is not sufficient evidence. Use synthetic prompts only and never attach secrets.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GitHub Copilot connector and the full local-gateway path described in the issue. Use a real Copilot-enabled account and synthetic prompts to verify device OAuth, credential persistence and refresh, model filtering, SSE text and tool calls, and error mapping. Done means all required evidence is captured and the current GitHub plan and policy permit the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, authentication, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100