Git Hosting

Resolve provider, host, repository/project, resource identity, and requested effect. Use an authenticated connector or provider CLI. Keep credentials out of output and command arguments.

Read provider semantics for IDs, pagination, API versions, errors, and ambiguous writes. Read GitHub workflows or GitLab workflows for endpoint payloads and operation-specific permissions.

Use native request schemas. Send only intended fields. Preserve literal multiline content through structured arguments or body files. Refresh the affected endpoint for a different server/API version or an uncovered field.