Conversation
Closes #136 (partial) - English version of contribution guide covering setup, workflow, commit conventions, review process, and coding standards. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
… spec, profiling guide, and hardware access - Add detailed review process steps - Add Kernel Design requirements (algorithm, data flow, roofline/80% target, trace viewer, precision) - Update branching strategy from fork-based to in-repo dev branches with CI check - Clarify tiered review policy (1 approve general, all-core-devs for cpu-ref) - Add profiling guide (xprof/TensorBoard Profiler setup and trace analysis) - Add hardware access section (SkyPilot scripts) - Include spec and plan documents Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe pull request adds standardized GitHub templates for bug reports and feature requests, a pull request template with development checklists, and comprehensive contribution guidelines ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request establishes the project's contribution framework by adding issue and pull request templates, a detailed contribution guide, and updating the README. The review feedback identifies several necessary corrections: updating the source directory path from src/ to tops/ in linting commands and the PR checklist, ensuring consistency in the design document directory paths, and removing a link to a non-existent Chinese version of the contributing guide.
|
|
||
| ## Contributing | ||
|
|
||
| We welcome contributions! Please read our [Contributing Guide](CONTRIBUTING.md) ([中文版](CONTRIBUTING.zh.md)) to get started. |
There was a problem hiding this comment.
The link to CONTRIBUTING.zh.md appears to be broken as the file is not included in this pull request. If the Chinese version of the contributing guide is not yet available, please remove this link to avoid 404 errors.
| We welcome contributions! Please read our [Contributing Guide](CONTRIBUTING.md) ([中文版](CONTRIBUTING.zh.md)) to get started. | |
| We welcome contributions! Please read our [Contributing Guide](CONTRIBUTING.md) to get started. |
|
|
||
| ```bash | ||
| # Lint | ||
| uv run ruff check src/ tests/ |
There was a problem hiding this comment.
| uv run ruff check src/ tests/ | ||
|
|
||
| # Format | ||
| uv run ruff format src/ tests/ |
|
|
||
| ## Kernel Design Requirements | ||
|
|
||
| Every new or refactored Kernel **must** have a design document in `docs/design/` covering the following: |
There was a problem hiding this comment.
There is a discrepancy in the design document path. ARCHITECTURE.md (the System of Record) specifies docs/design-docs/ops/ (line 42), while this file uses docs/design/. Please align them for consistency.
| Every new or refactored Kernel **must** have a design document in `docs/design/` covering the following: | |
| Every new or refactored Kernel **must** have a design document in docs/design-docs/ops/ covering the following: |
|
|
||
| ## Adding New Kernels | ||
|
|
||
| 1. Write a design document in `docs/design/` first. |
There was a problem hiding this comment.
|
|
||
| ## Checklist | ||
|
|
||
| - [ ] Code passes `uv run ruff check src/ tests/` and `uv run ruff format src/ tests/` |
Summary by CodeRabbit
Documentation
Chores