Problem
Steps 8-10 of the user journey require users to see git operations, but GitWorkflowManager is only used internally with no REST API exposure.
Current State
GitWorkflowManager exists at codeframe/git/workflow_manager.py
- Has
create_feature_branch(), commit_task_changes(), merge_to_main()
- Database has
git_branches table
- No API endpoints expose this functionality
Required Implementation
New Router: /api/projects/{id}/git/
POST /api/projects/{id}/git/branches # Create feature branch
GET /api/projects/{id}/git/branches # List branches
GET /api/projects/{id}/git/branches/{name} # Get branch details
POST /api/projects/{id}/git/commit # Commit changes
GET /api/projects/{id}/git/commits # List commits
GET /api/projects/{id}/git/status # Get working tree status
WebSocket Events to Add
branch_created - When feature branch created
commit_created - Already exists, verify it fires
Acceptance Criteria
Dependencies
- None (uses existing GitWorkflowManager)
Blocks
- #TBD (Git Commit UI)
- #TBD (PR Creation API)
Committee Report Reference
This was identified as a critical gap by 11/11 expert agents in the UX/UI committee review. Step 8 of the user journey is invisible without this API.
Updated Dependencies
Problem
Steps 8-10 of the user journey require users to see git operations, but
GitWorkflowManageris only used internally with no REST API exposure.Current State
GitWorkflowManagerexists atcodeframe/git/workflow_manager.pycreate_feature_branch(),commit_task_changes(),merge_to_main()git_branchestableRequired Implementation
New Router:
/api/projects/{id}/git/WebSocket Events to Add
branch_created- When feature branch createdcommit_created- Already exists, verify it firesAcceptance Criteria
git.pyrouter createdDependencies
Blocks
Committee Report Reference
This was identified as a critical gap by 11/11 expert agents in the UX/UI committee review. Step 8 of the user journey is invisible without this API.
Updated Dependencies