git-workflow

# git-workflow The opendray gateway exposes read-only git inspection endpoints backed by the `git` binary in the session's cwd, plus PR listing across configured hosts (GitHub, Gitea, GitLab). Use them instead of shelling out to `git` directly when you want structured output that's easy to summarise back to the user — falls back to plain `git` for anything not covered. ## When to use - User asks "what's changed", "status", "what files did I touch" - User wants to see a recent commit, a file's diff, or a PR list - Before committing, to verify staged vs unstaged - Before opening a PR, to check the diff against `HEAD` or origin For destructive ops (commit, push, branch, rebase, …) keep using the plain `git` CLI — those are not exposed via the gateway and are safer to run with the user's explicit confirmation. ## Endpoints (gateway runs at http://127.0.0.1:8770 by default) All endpoints accept `path=<absolute cwd>` and require the admin session token. Inside an opendray-spawned session, you can rely on the local gateway being reachable; `curl -s` works. ``` GET /api/v1/git/status?path=<dir> → branch, ahead/behind, files GET /api/v1/git/log?path=<dir>&n=20 → recent commits GET /api/v1/git/diff?path=<dir>&scope=all → unified diff (HEAD) GET /api/v1/git/diff?path=<dir>&scope=staged&file=<rel> GET /api/v1/git/show?path=<dir>&hash=<sha> → commit + patch GET /api/v1/git/remote?path=<dir> → owner/repo + token state GET /api/v1/git/prs?path=<dir>&sta...