--- title: "Rename or transfer a monorepo (owners)" description: "The label moves; the id, repos, history, members, Artifacts repos and\nfeeds stay. The old `owner/name` keeps working for the API and the git\ndoor (an alias) until that owner gives the name to another monorepo.\nA transfer (`owner`) goes to an organization the caller is in (else\n403 `not_your_namespace`), or to a person who already has their own\nowner row in it (else 400 `bad_owner`). Its own members stay; moved\ninto an org, the org's people gain it, and moved out, they lose it.\n409 `monorepo_exists` when the new name is taken. `replaced_alias`\nreports an old name of another monorepo that this one took over.\n" --- > 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 `PATCH /v1/monorepos/{owner}/{monorepo}` The label moves; the id, repos, history, members, Artifacts repos and feeds stay. The old `owner/name` keeps working for the API and the git door (an alias) until that owner gives the name to another monorepo. A transfer (`owner`) goes to an organization the caller is in (else 403 `not_your_namespace`), or to a person who already has their own owner row in it (else 400 `bad_owner`). Its own members stay; moved into an org, the org's people gain it, and moved out, they lose it. 409 `monorepo_exists` when the new name is taken. `replaced_alias` reports an old name of another monorepo that this one took over. ## Authentication Requires one of the following: - `credential`, http, header `Authorization` - `session`, apiKey, in cookie ## Path parameters - `renameMonorepo.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}$` - `renameMonorepo.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}$` ## Request body _Required._ - `renameMonorepo.name` (string, optional) — A monorepo name, unique within its owner: lower-case letters, digits, `.`, `_`, `-`; starts with a letter or digit; no `--`; at most 39 characters. Input in any case is lowered. Reserved, because /{owner}/{name} would be one of Pando's own pages: sessions (a person's recorded agent sessions). Creating or renaming to one answers 400 `reserved_name`. - pattern `^[a-z0-9](?:[a-z0-9._]|-(?!-)){0,38}$` - `renameMonorepo.owner` (string, optional) — 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}$` ## Example request ```json { "name": "string", "owner": "string" } ``` ## Code samples ### cURL ```curl curl --request PATCH \ --url https://app.gitpando.com/v1/monorepos/string/string \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --data ' { "name": "string", "owner": "string" } ' ``` ### TypeScript ```typescript const url = 'https://app.gitpando.com/v1/monorepos/string/string'; const options = { method: 'PATCH', headers: {'Content-Type': 'application/json', Authorization: 'Bearer '}, body: JSON.stringify({name: 'string', owner: 'string'}) }; 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" payload = { "name": "string", "owner": "string" } headers = { "Content-Type": "application/json", "Authorization": "Bearer " } response = requests.patch(url, json=payload, headers=headers) print(response.text) ``` ## Responses ### 200 Renamed #### Example ```json { "id": "string", "owner": "string", "name": "string", "full_name": "string", "kind": "monorepo", "created_at": "2019-08-24T14:15:22Z", "role": "owner", "owner_type": "user", "replaced_alias": { "full_name": "string", "pointed_to": "string" } } ``` - `renameMonorepo.response.200.id` (string, required) — Permanent: `m_` and 16 hex characters, or, for a monorepo made before namespaces, its old name. - `renameMonorepo.response.200.owner` (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}$` - `renameMonorepo.response.200.name` (string, required) — A monorepo name, unique within its owner: lower-case letters, digits, `.`, `_`, `-`; starts with a letter or digit; no `--`; at most 39 characters. Input in any case is lowered. Reserved, because /{owner}/{name} would be one of Pando's own pages: sessions (a person's recorded agent sessions). Creating or renaming to one answers 400 `reserved_name`. - pattern `^[a-z0-9](?:[a-z0-9._]|-(?!-)){0,38}$` - `renameMonorepo.response.200.full_name` (string, required) — `owner/name`. - `renameMonorepo.response.200.kind` (string, required) - one of `"monorepo"`, `"repo"` - `renameMonorepo.response.200.created_at` (string, required) - format `date-time` - `renameMonorepo.response.200.role` (string, required) — The caller's: the higher of their own row and, in an org's monorepo, their org role. - one of `"owner"`, `"member"` - `renameMonorepo.response.200.owner_type` (string, required) — Whose namespace `owner` is: a person's or an organization's. - one of `"user"`, `"org"` - `renameMonorepo.response.200.replaced_alias` (object | null, required) — An old `owner/name` (from a rename or transfer) that led to another monorepo and now leads to this one. Null when nothing was taken over. Never silent. - `renameMonorepo.response.200.replaced_alias.full_name` (string, required) — The old name, now this monorepo's. - `renameMonorepo.response.200.replaced_alias.pointed_to` (string | null, required) — The `owner/name` it led to before. ### 400 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" } ] } } } ``` - `renameMonorepo.response.400.error` (object, required) - `renameMonorepo.response.400.error.code` (string, required) - `renameMonorepo.response.400.error.message` (string, required) - `renameMonorepo.response.400.error.paths` (array, optional) - `renameMonorepo.response.400.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing. - `renameMonorepo.response.400.error.checks.sha` (string | null, required) - `renameMonorepo.response.400.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"` - `renameMonorepo.response.400.error.checks.required` (array | null, required) — Null while unknown. - `renameMonorepo.response.400.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. - `renameMonorepo.response.400.error.checks.statuses` (array, required) — The latest status per context. - `renameMonorepo.response.400.error.checks.statuses.sha` (string, required) - `renameMonorepo.response.400.error.checks.statuses.context` (string, required) - `renameMonorepo.response.400.error.checks.statuses.state` (string, required) - one of `"pending"`, `"success"`, `"failure"`, `"error"` - `renameMonorepo.response.400.error.checks.statuses.created_at` (string, required) - format `date-time` - `renameMonorepo.response.400.error.checks.statuses.target_url` (string | null, optional) - `renameMonorepo.response.400.error.checks.statuses.description` (string | null, optional) - `renameMonorepo.response.400.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. - `renameMonorepo.response.400.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. - `renameMonorepo.response.400.error.checks.missing` (array, optional) ### 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" } ] } } } ``` - `renameMonorepo.response.403.error` (object, required) - `renameMonorepo.response.403.error.code` (string, required) - `renameMonorepo.response.403.error.message` (string, required) - `renameMonorepo.response.403.error.paths` (array, optional) - `renameMonorepo.response.403.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing. - `renameMonorepo.response.403.error.checks.sha` (string | null, required) - `renameMonorepo.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"` - `renameMonorepo.response.403.error.checks.required` (array | null, required) — Null while unknown. - `renameMonorepo.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. - `renameMonorepo.response.403.error.checks.statuses` (array, required) — The latest status per context. - `renameMonorepo.response.403.error.checks.statuses.sha` (string, required) - `renameMonorepo.response.403.error.checks.statuses.context` (string, required) - `renameMonorepo.response.403.error.checks.statuses.state` (string, required) - one of `"pending"`, `"success"`, `"failure"`, `"error"` - `renameMonorepo.response.403.error.checks.statuses.created_at` (string, required) - format `date-time` - `renameMonorepo.response.403.error.checks.statuses.target_url` (string | null, optional) - `renameMonorepo.response.403.error.checks.statuses.description` (string | null, optional) - `renameMonorepo.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. - `renameMonorepo.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. - `renameMonorepo.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" } ] } } } ``` - `renameMonorepo.response.409.error` (object, required) - `renameMonorepo.response.409.error.code` (string, required) - `renameMonorepo.response.409.error.message` (string, required) - `renameMonorepo.response.409.error.paths` (array, optional) - `renameMonorepo.response.409.error.checks` (object, optional) — GitHub's combined status, plus the required contexts and which are missing. - `renameMonorepo.response.409.error.checks.sha` (string | null, required) - `renameMonorepo.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"` - `renameMonorepo.response.409.error.checks.required` (array | null, required) — Null while unknown. - `renameMonorepo.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. - `renameMonorepo.response.409.error.checks.statuses` (array, required) — The latest status per context. - `renameMonorepo.response.409.error.checks.statuses.sha` (string, required) - `renameMonorepo.response.409.error.checks.statuses.context` (string, required) - `renameMonorepo.response.409.error.checks.statuses.state` (string, required) - one of `"pending"`, `"success"`, `"failure"`, `"error"` - `renameMonorepo.response.409.error.checks.statuses.created_at` (string, required) - format `date-time` - `renameMonorepo.response.409.error.checks.statuses.target_url` (string | null, optional) - `renameMonorepo.response.409.error.checks.statuses.description` (string | null, optional) - `renameMonorepo.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. - `renameMonorepo.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. - `renameMonorepo.response.409.error.checks.missing` (array, optional) Source: https://docs.gitpando.com/api/monorepos/renameMonorepo/index.md