system

Set Gitlab Username

The one-time step for mapping the NEXT GitLab username (F10): a person with system:credentials:write picks the Roost principal and types the gitlab.com username GitLab itself shows as that person's assignee -- never guessed, never inferred from a name.

Refuses (422) a principal that is not kind = 'human' or is removed_at IS NOT NULL -- app.modules.issues.gitlab_watch would never resolve either kind of row anyway (_mapped_principals, _resolve_assignees both filter on exactly this), so accepting the write and having it silently do nothing is worse than refusing it here with a reason. Refuses (409) a username already mapped to a DIFFERENT principal -- principals_gitlab_username_unique_idx (migration 0642) is the floor under this; this route's own read-before-write check is what turns that floor into a message a person can act on instead of a bare UniqueViolationError.

put/api/system/gitlab/principal-mapping

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/system/gitlab/principal-mapping
  • Auth: none declared

Request body

principal_idstring uuid required
gitlab_usernamestring required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.