What problem does it solve?
Workers often need to run authenticated Git operations (clone, fetch, push) but lack direct access to Git credentials, causing failures or unsafe handling of secrets.
Core Features & Use Cases
- Delegates any git command that needs authentication: Worker sends a
git-request: message to the Manager, and the Manager executes the Git operations using credentials the Worker cannot access.
- Supports full repo lifecycle workflows: cloning, branch creation/switching, staging/committing, pushing, rebasing, merging, and more.
- Clear request/response contract: returns
git-result: on success or git-failed: with error details on failure, enabling a controlled and auditable workflow.
Use case example: A Worker needs to create a feature branch, modify files, commit changes, and push the branch to a remote repository; it delegates clone/checkout/add/commit/push to the Manager while keeping credentials on the Manager side.
Quick Start
Ask your Worker to send a single git-request: to the Manager containing the target workspace and the complete list of Git operations to execute, with intent included in the CONTEXT block.