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-lockfile then pnpm verify (or pnpm verify --profile docs for 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.
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)
editreplace_allcorrupts literal$sequencesMCODE_PROVIDER_API_KEYnot stripped in scrub modecloneContextWithdropsisFileprobePOST /api/file/savecannot create new filesHappy 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)Thanks for considering the invite. If there's a preferred process (invite vs. alternate contribution path), please point me at it.