mirror of
https://github.com/radixark/miles.git
synced 2026-11-04 08:25:29 +08:00
04b61f31a1
Co-authored-by: Zhichen Zeng <zczeng@uw.edu> Co-authored-by: Shi Dong <shi.dong@radixark.ai> Co-authored-by: Yueming Yuan <yym022502@gmail.com> Co-authored-by: Shi-Dong <Shi-Dong@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Ethan (Yusheng) Su <yushengsu.thu@gmail.com> Co-authored-by: Haoguang Cai <kai.cai@radixark.ai> Co-authored-by: Mingyi Lu <wisclmy0611@gmail.com> Co-authored-by: Jiajun Li <guapisolo@gmail.com>
1.4 KiB
1.4 KiB
title, description
| title | description |
|---|---|
| Developer Guide | Architecture, contribution conventions, debugging, and migration notes. |
You're here because you want to change Miles, not just use it. This section is the short tour for new contributors.
PR conventions, code layout, how reviews work.
Aligning precision, separate train/rollout debugging, common kernel pitfalls.
Sync → async loop, breaking flag changes between releases.
The 30-minute tour of how Miles is organized internally.
Opt-in backends and features (FSDP, …) that aren't production-ready yet.
TL;DR for first-time contributors
- Pick something small from
good first issueon GitHub. - Run the Reproducibility recipe so you can be sure "I changed X and it broke" actually means that.
- Use
--debug-train-onlyor--debug-rollout-onlyto scope your changes. - Open a PR. We'll review within ~48h.