---
title: "git.checks.write · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/git.checks.write"
updated: null
---

# git.checks.write · OpenVibe.Services

HTML: [git.checks.write · OpenVibe.Services](https://openvibe.services/docs/capabilities/git.checks.write)

# `git.checks.write`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

Not grantable to apps (active, first-party).

Report commit statuses (checks) on OpenVibe.Git (git.openvibe.codes): POST /api/v1/repos/:owner/:name/commits/:sha/statuses with {context, state: pending|success|failure|error, description?, target\_url?}. A first-party CI service (Run first) holds this capability for the audience openvibe.git and reports any repository it builds; the owner may report their own. Reads (GET, the latest per context) need no capability on a public repository and git.repo.read on a private one. A change is mergeable only when its required contexts are green.

- Owner: git (token audience `openvibe.git`)
- Version: 1.0
- Status: active
- Visibility: first-party
- Resource constraints: owner
- Quota class: standard
- Permissions: git:checks-write
- Input: [git.access-request@1](/docs/contracts/git.access-request)
- Output: git.access-result@1
- Events: —
- Implemented by: - `POST /api/v1/repos/:owner/:name/commits/:sha/statuses`

[These routes in the API explorer](/docs/api/git#cap-git.checks.write)