fix(create-milestones): clarify loop structure for assigning issues

Restructure steps 7-8 to be clearer and more efficient:
- Merged "Assign Issues" and "Apply Labels" into single step
- Explicit nested loop structure: milestone → issues in that milestone
- Process one milestone at a time
- Combine milestone assignment + labels in single tea command
- Added clear examples
- Prevents confusion about looping and when to move on

Before: Separate loops for milestone assignment and label application
After: Single pass through milestones, process all issues per milestone

Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
2026-01-12 19:27:08 +01:00
parent fd713c8697
commit dd97378bb9

View File

@@ -148,28 +148,42 @@ tea milestones create \
Capture milestone ID/title for issue assignment.
### 7. Assign Issues to Milestones
### 7. Assign Issues and Apply Labels
For each issue in each milestone:
**For each milestone, process all its issues:**
```bash
tea issues edit <issue-number> --milestone "<milestone-title>"
# For each milestone:
for milestone in milestones:
# For each issue in this milestone:
for issue in milestone.issues:
# Combine milestone assignment + labels in single command
tea issues edit <issue-number> \
--milestone "<milestone-title>" \
--labels "<existing-labels>,<value-label>,<risk-label-if-applicable>"
```
### 8. Apply Value/Risk Labels
For each issue:
**Example:**
```bash
tea issues edit <issue-number> --labels "<existing-labels>,<value-label>"
# Issue #42 in "Customer can register and authenticate" milestone
tea issues edit 42 \
--milestone "Customer can register and authenticate" \
--labels "bounded-context/auth,value/high"
# If has risk
tea issues edit <issue-number> --labels "<existing-labels>,<value-label>,risk/high"
# Issue #43 with risk
tea issues edit 43 \
--milestone "Customer can register and authenticate" \
--labels "bounded-context/auth,value/high,risk/high"
```
**Preserve existing labels** (bounded-context, capability, etc.)
**Important:**
- Process one milestone at a time, all issues in that milestone
- Preserve existing labels (bounded-context, capability, etc.)
- Add value label for all issues
- Add risk/high only if issue has technical risk
- Combine milestone + labels in single `tea issues edit` command (efficient)
### 9. Report Results
### 8. Report Results
Show created milestones with links: