Create or update a commit status

POST/api/repos/{owner}/{repo}/commits/{sha}/statuses

createCommitStatus

Attaches an external check result to a commit. One live status per `context` per commit — re-posting a context replaces its state (latest-wins). Requires write access on the repository.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X POST 'https://neosource.dev/api/repos/OWNER/REPO/commits/SHA/statuses' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"context":"string","state":"string"}'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/commits/SHA/statuses", {
  method: "POST",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"context":"string","state":"string"}),
});

Path parameters

ownerrequired: Repository owner or organization slug.
string
reporequired: Repository name.
string
sharequired: The 40-hex SHA-1 commit object ID.
string
ownerrequired: string
reporequired: string
sharequired: string

Request bodyrequired

application/json

CommitStatusRequest

object

Body of `POST .../commits/{sha}/statuses` — create or replace the status for a context (latest-wins on `(repo, sha, context)`).

contextrequired: string
Check name the status is filed under (e.g. `ci/lint`). One live status per context per commit. Open vocabulary by design — external CI systems choose their own contexts.
description: string | null
Short human-readable summary of the result.
staterequired: CommitStatusState
string
State of a single commit status, GitHub-shaped. `Error` is distinct from `Failure` on individual statuses (infrastructure/tooling breakage vs. a real red result) but the combined rollup folds both into `Failure`.
"pending""success""failure""error"
target_url: string | null
Link to the external system's detail page for this check.

Responses

201Status recorded

application/json

CommitStatusResponse

object

actor_id: string | null
Account that posted the status.
contextrequired: string
created_atrequired: integerint64
description: string | null
idrequired: string
repo_idrequired: string
sharequired: string
40-hex git SHA-1 of the commit the status is attached to.
staterequired: CommitStatusState
string
State of a single commit status, GitHub-shaped. `Error` is distinct from `Failure` on individual statuses (infrastructure/tooling breakage vs. a real red result) but the combined rollup folds both into `Failure`.
"pending""success""failure""error"
target_url: string | null
updated_atrequired: integerint64

Standard errors

Bodies documented once for the whole API — see standard errors.

400Bad Request — one of: invalid_input
401Authentication required
403Forbidden — one of: forbidden
404Not Found — one of: not_found
409Conflict — one of: already_exists, conflict, non_fast_forward
423Locked — one of: busy
429Rate limited — retry after the `Retry-After` header
500Internal server error
503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
504Gateway timeout — the request exceeded the server's handling budget