Harthelm Docs
REST APIGit

List the repositories the workspace may use

The git proxy allows exactly these repositories for the workspace.

Generated from openapi/harthelm.yaml at v1.5.0
GET
/workspaces/{ws}/git-access

Authorization

cookie__Host-harthelm_session<token>

Browser session of the UI (12 h idle, 7 days absolute). State-changing requests also need the header Harthelm-CSRF: 1 and a matching Origin.

Path Parameters

ws*integer

Numeric resource id.

Formatint64
Range1 <= value

Query Parameters

limit?integer

Maximum number of items per page.

Range1 <= value <= 200
Default50
cursor?string

Opaque cursor from next_cursor of the previous page.

Lengthlength <= 1024

Response Body

A page of entries, the origin repository first.

application/json
  1. response
next_cursor?string

Absent on the last page.

items*array<>
curl -X GET 'https://console.example.com/api/v1/workspaces/1/git-access'
{  "next_cursor": "string",  "items": [    {      "provider": "string",      "repo": "string",      "access": "read",      "origin": true,      "added_by": 1,      "created_at": "2019-08-24T14:15:22Z"    }  ]}

List the team's default repositories

Repositories every new workspace of the team may use through the git proxy.

Pull the current branch

`git pull --ff-only` in `/data/app` through the git proxy, as the workspace. It never syncs the landscape. A pull git refuses answers 409 with problem `git-pull-failed` and git's output as `detail`. Needs `workspace.code`; 409 when the IDE does not run.