abbyswag/qwen-code
1
0
Fork 0
mirror of https://github.com/QwenLM/qwen-code.git synced 2025-12-19 09:33:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update common workflows and quickstart sections for clarity and formatting

Browse Source
This commit is contained in:
joeytoday
2025-12-12 10:15:28 +08:00
parent 9fd4f58c16
commit 779ed2cda4
2 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/users/common-workflow.md
View File

@@ -449,15 +449,15 @@ Use arrow keys to navigate and press Enter to select a conversation. Press Esc t
> qwen --continue --p "Run the tests again" > qwen --continue --p "Run the tests again"
> ``` > ```
## Run parallel Qwen Code sessions with Git worktrees【TBD 不是特别理解创建 worktree，需要确认一下命令】 ## Run parallel Qwen Code sessions with Git worktrees
Suppose you need to work on multiple tasks simultaneously with complete code isolation between Qwen Code instances. Suppose you need to work on multiple tasks simultaneously with complete code isolation between Qwen Code instances.
1. Understand Git worktrees **1. Understand Git worktrees**
Git worktrees allow you to check out multiple branches from the same repository into separate directories. Each worktree has its own working directory with isolated files, while sharing the same Git history. Learn more in the [official Git worktree documentation](https://git-scm.com/docs/git-worktree). Git worktrees allow you to check out multiple branches from the same repository into separate directories. Each worktree has its own working directory with isolated files, while sharing the same Git history. Learn more in the [official Git worktree documentation](https://git-scm.com/docs/git-worktree).
2. Create a new worktree **2. Create a new worktree**
```bash ```bash
# Create a new worktree with a new branch # Create a new worktree with a new branch
@@ -469,7 +469,7 @@ git worktree add ../project-bugfix bugfix-123
This creates a new directory with a separate working copy of your repository. This creates a new directory with a separate working copy of your repository.
4. Run Qwen Code in each worktree **3. Run Qwen Code in each worktree**
```bash ```bash
# Navigate to your worktree # Navigate to your worktree
@@ -479,14 +479,14 @@ cd ../project-feature-a
qwen qwen
``` ```
5. Run Qwen Code in another worktree **4. Run Qwen Code in another worktree**
```bash ```bash
cd ../project-bugfix cd ../project-bugfix
qwen qwen
``` ```
6. Manage your worktrees **5. Manage your worktrees**
```bash ```bash
# List all worktrees # List all worktrees

6
docs/users/quickstart.md
View File

@@ -186,7 +186,7 @@ review my changes and suggest improvements
> [!tip] > [!tip]
> **Remember**: Qwen Code is your AI pair programmer. Talk to it like you would a helpful colleague - describe what you want to achieve, and it will help you get there. > **Remember**: Qwen Code is your AI pair programmer. Talk to it like you would a helpful colleague - describe what you want to achieve, and it will help you get there.
## 🧭 Essential commands ## Essential commands
Here are the most important commands for daily use: Here are the most important commands for daily use:
@@ -206,7 +206,7 @@ Here are the most important commands for daily use:
See the [CLI reference](/users/reference/cli-reference) for a complete list of commands. See the [CLI reference](/users/reference/cli-reference) for a complete list of commands.
## 📌 Pro tips for beginners ## Pro tips for beginners
- Be specific with your requests - Be specific with your requests
- Instead of: "fix the bug" - Instead of: "fix the bug"
@@ -236,7 +236,7 @@ See the [CLI reference](/users/reference/cli-reference) for a complete list of c
- Press ↑ for command history - Press ↑ for command history
- Type `/` to see all slash commands - Type `/` to see all slash commands
## 🙋🏻 Getting help ## Getting help
- **In Qwen Code**: Type `/help` or ask "how do I..." - **In Qwen Code**: Type `/help` or ask "how do I..."
- **Documentation**: You're here! Browse other guides - **Documentation**: You're here! Browse other guides