Create or Append Note
Attach text to a Git object without changing the repository contents. Use notes for review markers, internal decisions, or other lightweight context.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Repository name. Names that contain / or any other character that is not safe in a URL path segment must be URL encoded so the value occupies a single path segment. For example pierre/example is sent as pierre%2Fexample. Plain names such as example can be sent as-is. The server URL-decodes the value before resolving the repository.
Body
Create, replace, or append a Git note for the supplied SHA. When action is omitted the server behaves as though add was supplied.
Notes write request describing the commit, the action (add, append, or remove), the note content, and optional concurrency guard.
Git object SHA to attach the note to.
"b003fc78805954584e1ee364a4ad39d7c79e819a"
add replaces any existing note. append adds new text to the existing note body.
Author object with name and email for the notes commit.
Optional compare-and-swap guard for the notes ref.
Plain-text note content. Required for add and append.
Response
Note update applied to the notes ref.
Result of a notes write operation, including the resulting notes ref state.
New notes ref SHA after the operation.
"3a1d9f7d6b6d482c970554e2a6ef980ecf4f1d55"
Operation result with success, status, and optional message.
The commit SHA the note is attached to.
"b003fc78805954584e1ee364a4ad39d7c79e819a"
The notes reference (refs/notes/commits).
"refs/notes/commits"
Previous notes ref commit SHA.
"0c8b5bb9d550d58fcfd651a4fdce8024ef7f1492"