mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-04-28 03:30:40 +00:00
bf5aa685c2
Move "Dive Deeper" section after "Screenshots / Video Demo" to improve readability. Screenshots section is more actionable and should appear earlier in the template. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
54 lines
1.7 KiB
Markdown
54 lines
1.7 KiB
Markdown
## TLDR
|
|
|
|
<!-- Add a brief description of what this pull request changes and why and any important things for reviewers to look at -->
|
|
|
|
## Screenshots / Video Demo
|
|
|
|
<!--
|
|
Please attach a screenshot or short video showing your change in action.
|
|
This helps reviewers understand the change quickly and prioritize reviews.
|
|
|
|
- For bug fixes: show the before/after behavior.
|
|
- For features: show the new functionality in use.
|
|
- For refactors or internal changes with no visible effect: write "N/A — no user-facing change" and briefly explain why.
|
|
|
|
PRs with visual demos typically get reviewed much faster!
|
|
-->
|
|
|
|
## Dive Deeper
|
|
|
|
<!-- more thoughts and in-depth discussion here -->
|
|
|
|
## Reviewer Test Plan
|
|
|
|
<!-- when a person reviews your code they should ideally be pulling and running that code. How would they validate your change works and if relevant what are some good classes of example prompts and ways they can exercise your changes -->
|
|
|
|
## Testing Matrix
|
|
|
|
<!-- Before submitting please validate your changes on as many of these options as possible -->
|
|
|
|
| | 🍏 | 🪟 | 🐧 |
|
|
| -------- | --- | --- | --- |
|
|
| npm run | ❓ | ❓ | ❓ |
|
|
| npx | ❓ | ❓ | ❓ |
|
|
| Docker | ❓ | ❓ | ❓ |
|
|
| Podman | ❓ | - | - |
|
|
| Seatbelt | ❓ | - | - |
|
|
|
|
## Linked issues / bugs
|
|
|
|
<!--
|
|
Link to any related issues or bugs.
|
|
|
|
**If this PR fully resolves the issue, use one of the following keywords to automatically close the issue when this PR is merged:**
|
|
|
|
- Closes #<issue_number>
|
|
- Fixes #<issue_number>
|
|
- Resolves #<issue_number>
|
|
|
|
*Example: `Resolves #123`*
|
|
|
|
**If this PR is only related to an issue or is a partial fix, simply reference the issue number without a keyword:**
|
|
|
|
*Example: `This PR makes progress on #456` or `Related to #789`*
|
|
-->
|