Point a ref at an existing revision

PUT 
/api/v1/projects/:project_id/refs/:ref_name

Create or move a named ref onto an existing project revision.

Ref names are git-refname-ish validated; the revision must belong to this project. Moving the default ref also moves the project head.

• Scope required: projects:manage_source + manager-or-above.
• Archived projects reject the move (409).

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.