--- title: "Remove a user's own row from the monorepo (owners; a person's monorepo keeps one owner)" description: "Removes their own row only (404 when they have none); someone in the owning org keeps the org's access. An org's monorepo needs no owner row of its own (its org's owners own it)." --- > Documentation Index > Fetch the complete documentation index at: https://docs.gitpando.com/llms.txt > Use this file to discover all available pages before exploring further. Path: Pando API › monorepos `DELETE /v1/monorepos/{owner}/{monorepo}/members/{login}` Removes their own row only (404 when they have none); someone in the owning org keeps the org's access. An org's monorepo needs no owner row of its own (its org's owners own it). ## Authentication Requires one of the following: - `credential`, http, header `Authorization` - `session`, apiKey, in cookie ## Path parameters - `removeMember.path.owner` (string, required) — The monorepo's owner, a namespace (a person's login or an organization). Matched without case. - pattern `^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$` - `removeMember.path.monorepo` (string, required) — The monorepo's name within its owner (or an old name). Matched without case. - pattern `^[a-z0-9](?:[a-z0-9._]|-(?!-)){0,38}$` - `removeMember.path.login` (string, required) — A user's login, which is their namespace, or an organization's (one space for both): 1 to 39 lower-case letters, digits and single hyphens, no hyphen at either end (input in any case is lowered). Reserved, because a namespace is the first URL segment: v1, healthz, login, logout, settings, assets, fonts, new, api, app, static, orgs, users, docs, install. A login made at sign-in comes from the email's local part, skipping reserved and taken names (`base`, `base-2`, ... `base-999`, then a random tail). - pattern `^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$` ## Code samples ### cURL ```curl curl --request DELETE \ --url https://app.gitpando.com/v1/monorepos/string/string/members/string \ --header 'Authorization: Bearer ' ``` ### TypeScript ```typescript const url = 'https://app.gitpando.com/v1/monorepos/string/string/members/string'; const options = {method: 'DELETE', headers: {Authorization: 'Bearer '}}; fetch(url, options) .then(res => res.json()) .then(json => console.log(json)) .catch(err => console.error(err)); ``` ### Python ```python import requests url = "https://app.gitpando.com/v1/monorepos/string/string/members/string" headers = {"Authorization": "Bearer "} response = requests.delete(url, headers=headers) print(response.text) ``` ## Responses ### 204 Removed ### 403 An error #### Example ```json { "error": { "code": "string", "message": "string", "paths": [ "string" ], "checks": { "sha": "string", "state": "success", "required": [ "string" ], "checks_unknown": "string", "missing": [ "string" ], "statuses": [ { "sha": "string", "context": "string", "state": "pending", "target_url": "string", "description": "string", "creator": "string", "app": "string", "created_at": "2019-08-24T14:15:22Z" } ] } } } ``` - `removeMember.response.403.error` (object, required) - `removeMember.response.403.error.code` (string, required) - `removeMember.response.403.error.message` (string, required) - `removeMember.response.403.error.paths` (array, optional) - `removeMember.response.403.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing. - `removeMember.response.403.error.checks.sha` (string | null, required) - `removeMember.response.403.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused). - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"` - `removeMember.response.403.error.checks.required` (array | null, required) — Null while unknown. - `removeMember.response.403.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise. - `removeMember.response.403.error.checks.statuses` (array, required) — The latest status per context. - `removeMember.response.403.error.checks.statuses.sha` (string, required) - `removeMember.response.403.error.checks.statuses.context` (string, required) - `removeMember.response.403.error.checks.statuses.state` (string, required) - one of `"pending"`, `"success"`, `"failure"`, `"error"` - `removeMember.response.403.error.checks.statuses.created_at` (string, required) - format `date-time` - `removeMember.response.403.error.checks.statuses.target_url` (string | null, optional) - `removeMember.response.403.error.checks.statuses.description` (string | null, optional) - `removeMember.response.403.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:` for a status posted with a status token or by a CI integration; `hook:` for a status token from a web hook with no app. - `removeMember.response.403.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows. - `removeMember.response.403.error.checks.missing` (array, optional) ### 409 An error #### Example ```json { "error": { "code": "string", "message": "string", "paths": [ "string" ], "checks": { "sha": "string", "state": "success", "required": [ "string" ], "checks_unknown": "string", "missing": [ "string" ], "statuses": [ { "sha": "string", "context": "string", "state": "pending", "target_url": "string", "description": "string", "creator": "string", "app": "string", "created_at": "2019-08-24T14:15:22Z" } ] } } } ``` - `removeMember.response.409.error` (object, required) - `removeMember.response.409.error.code` (string, required) - `removeMember.response.409.error.message` (string, required) - `removeMember.response.409.error.paths` (array, optional) - `removeMember.response.409.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing. - `removeMember.response.409.error.checks.sha` (string | null, required) - `removeMember.response.409.error.checks.state` (string, required) — `success` when the merge gate passes; `missing` when a required context has not reported; `unknown` while the required checks are (an unforced merge is refused). - one of `"success"`, `"pending"`, `"failure"`, `"error"`, `"missing"`, `"unknown"` - `removeMember.response.409.error.checks.required` (array | null, required) — Null while unknown. - `removeMember.response.409.error.checks.checks_unknown` (string | null, required) — Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise. - `removeMember.response.409.error.checks.statuses` (array, required) — The latest status per context. - `removeMember.response.409.error.checks.statuses.sha` (string, required) - `removeMember.response.409.error.checks.statuses.context` (string, required) - `removeMember.response.409.error.checks.statuses.state` (string, required) - one of `"pending"`, `"success"`, `"failure"`, `"error"` - `removeMember.response.409.error.checks.statuses.created_at` (string, required) - format `date-time` - `removeMember.response.409.error.checks.statuses.target_url` (string | null, optional) - `removeMember.response.409.error.checks.statuses.description` (string | null, optional) - `removeMember.response.409.error.checks.statuses.creator` (string, optional) — The member who posted it (a login); `app:` for a status posted with a status token or by a CI integration; `hook:` for a status token from a web hook with no app. - `removeMember.response.409.error.checks.statuses.app` (string | null, optional) — The CI service that reported it (`buildkite`, `github-actions`, ...), stamped by Pando from a status token or a CI integration, never from the body or `target_url`. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows. - `removeMember.response.409.error.checks.missing` (array, optional) Source: https://docs.gitpando.com/api/monorepos/removeMember/index.md