git-delegation-management

You can use Git delegation to let a Manager execute clone, commit, push, and rebase operations on behalf of Workers. Workers send structured git-request messages without needing host-configured Git credentials. The Manager processes these requests using host-mounted authentication and returns git-result or git-failed responses.

Shared repository state is coordinated using a task-scoped workspace synced via MinIO. This setup allows multiple agents to collaborate on the same repository with controlled state, reducing workspace collisions through conflict-aware processing markers during Git operations.

Format a Git request message by including a workspace path and an operations list. The Manager executes the specified Git workflow, such as clone, checkout a branch, commit, and push, then replies with a structured git-result or git-failed response indicating the outcome.

Yes, Git delegation uses MinIO synchronization to maintain shared workspace state across multiple agents. This integration ensures that task-scoped workspaces remain consistent during collaborative repository workflows, preventing state collisions.

Delegated Git operations may fail and return git-failed responses due to workspace collisions or missing host-mounted Git configuration. The system uses processing markers to coordinate tasks safely, but incorrect workspace paths or credential issues on the host can cause execution failures.

Credential delegation requires host-mounted Git configuration and credentials on the Manager side. Workers cannot execute Git commands directly and must rely on structured git-request messages, meaning the Manager must be available to process operations and handle MinIO synchronization.