mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
Git integration and Project workspace fixes
This commit is contained in:
@@ -63,15 +63,34 @@ roboco_git_create_branch(project_slug, task_id, branch_type, parent_branch)
|
||||
```
|
||||
|
||||
- **branch_type**: `feature`, `bug`, `chore`, `docs`, `hotfix`
|
||||
- **parent_branch**: Parent task's branch (or `main` for top-level)
|
||||
- **parent_branch**: Parent task's branch (or project's default branch for top-level)
|
||||
- Branch naming: `{type}/{team}/{task_id}` (auto-generated)
|
||||
|
||||
**Example:**
|
||||
```
|
||||
roboco_git_create_branch("roboco", "abc123", "feature", "main")
|
||||
roboco_git_create_branch("roboco", "abc123", "feature")
|
||||
# Creates: feature/backend/abc123
|
||||
```
|
||||
|
||||
**Branch Hierarchy (when using hierarchical branching):**
|
||||
Branches are typically created top-down:
|
||||
1. Main PM creates root branch from default branch
|
||||
2. You create subtask branch from root branch
|
||||
3. Dev works on subsubtask branch from your branch
|
||||
|
||||
**When creating a subtask branch:**
|
||||
- Check if parent task has a branch set
|
||||
- If so, use parent's branch as `parent_branch` parameter
|
||||
- If branching from default branch directly, that works too
|
||||
|
||||
**Branch hierarchy example:**
|
||||
```
|
||||
default (main/master/etc)
|
||||
└─ feature/backend/ROOT123 ← Main PM's branch
|
||||
└─ feature/backend/ROOT123/SUB456 ← Your branch
|
||||
└─ feature/backend/ROOT123/SUB456/DEV789 ← Dev branch
|
||||
```
|
||||
|
||||
### 6. ACTIVATE
|
||||
`roboco_task_activate()` moves backlog → pending. Now visible to devs.
|
||||
|
||||
@@ -175,6 +194,12 @@ When ALL subtasks done: reflect + complete your task.
|
||||
6. **Pause after delegating** - Don't spin waiting
|
||||
7. **Reflect before complete** - `roboco_journal_reflect()` required
|
||||
|
||||
**Task Delegation Options:**
|
||||
- `roboco_task_assign()` - Reassign an existing task to a different agent
|
||||
- `roboco_task_create(parent_task_id=...)` - Create a subtask under your task
|
||||
|
||||
For coordination tasks where you're managing work, subtasks are often cleaner for tracking.
|
||||
|
||||
## CEO Escalation
|
||||
|
||||
For major tasks, escalate to CEO instead of completing directly:
|
||||
|
||||
@@ -30,13 +30,23 @@ Claim → read full description → plan breakdown across cells → start → jo
|
||||
### 3. CREATE PARENT BRANCH (Git Tasks)
|
||||
**For tasks with `requires_git=True`:**
|
||||
```
|
||||
roboco_git_create_branch(project_slug, task_id, branch_type, "main")
|
||||
roboco_git_create_branch(project_slug, task_id, branch_type)
|
||||
```
|
||||
|
||||
- Creates parent branch from `main`
|
||||
- Creates parent branch from the project's default branch (e.g., `main`, `master`)
|
||||
- Cell PM subtask branches will fork from this
|
||||
- Example: `feature/cross/abc123` for cross-cell work
|
||||
|
||||
**Branch Hierarchy for Git Tasks:**
|
||||
- For hierarchical branching: default branch → Your branch → Cell PM branch → Dev branch
|
||||
- If using hierarchical branches, create root branch before Cell PMs create theirs
|
||||
- Cell PM branches fork from your branch (set as `parent_branch`)
|
||||
|
||||
**Typical order for hierarchical branching:**
|
||||
1. Create your root branch from project's default branch
|
||||
2. Create cell tasks, Cell PMs create branches from your branch
|
||||
3. Devs create branches from Cell PM branches
|
||||
|
||||
### 4. CREATE GROUP
|
||||
Use `roboco_group_create()` in each relevant cell channel. Cell PMs need groups to create sessions.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user