Fetch a VCS ref and append it as a revision

POST 
/api/v1/projects/:project_id/revisions

Explicit VCS fetch-append. VCS-source projects only.

Appends under ref_name (default production); a new name creates a candidate branch off the default ref's head. Identical bytes to the ref head short-circuit to the existing row. Archive projects use POST /revisions/upload instead.

• Scope required: projects:manage_source + manager-or-above.
• Archived projects reject the append (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.