MiniMax-AI / MiniMax-AI/minimax-code
Request: collaborator access to contribute bug fixes (Frank-zhu0404)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 141
- Avg merge
- 2h 45m
- Merged PRs (30d)
- 46
Description
Summary
Hi maintainers — I'd like to request repository collaborator access for GitHub user Frank-zhu0404.
Per CONTRIBUTING.md, code/docs PRs are currently accepted only from collaborators. I have a short list of small, already-scoped bug fixes I'd like to submit as proper PRs once access is granted.
Proposed first PRs (small / clear)
| Issue | Scope |
|---|---|
| #143 | README Download buttons are non-clickable images (docs-only; keep EN + ZH in sync) |
| #154 | Offline smoke tests fail when ambient HTTP(S)_PROXY is set (CI harness) |
| #155 | edit replace_all corrupts literal $ sequences |
| #153 | MCODE_PROVIDER_API_KEY not stripped in scrub mode |
| #151 | cloneContextWith drops isFile probe |
| #150 | Bash deny rules skip transparent wrappers (allow does not) |
| #149 | POST /api/file/save cannot create new files |
| #152 | Context compaction trigger stays tripped after compaction |
Happy to start with #143 (docs-only) and #154 (smoke/proxy) as the first two.
Validation I will run before any PR
pnpm install --frozen-lockfilethenpnpm verify(orpnpm verify --profile docsfor docs-only)- Fill the PR template (Change / Validation / publication checkboxes / maintainer handoff)
- No secrets or private history in commits
Thanks for considering the invite. If there's a preferred process (invite vs. alternate contribution path), please point me at it.
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
Read CONTRIBUTING.md to confirm the collaborator-only contribution process and review the requested access for Frank-zhu0404. Done means the maintainer either grants repository collaborator access or documents an alternate path for submitting the listed fixes; #143 and #154 are identified as the proposed first PRs.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100