Cherry-pick commit

Cherry-picks changes from a specific commit (identified by ref_id) into the current workspace.

Process:

• Creates a temporary patch from the source commit
• Applies it to the workspace
• If conflicts occur, returns a merge ID that must be resolved before proceeding

Requirements: Requires WRITE access.

Returns:

• 404 Not Found if the reference doesn’t exist
• 202 Accepted with merge_id if conflicts occurred
• 204 No Content on clean application

POST /repos/{repo_id}/workspaces/{workspace_id}/cherry-pick

Cherry-pick commit

cURL

curl --request POST \
  --url https://api.diversion.dev/v0/repos/{repo_id}/workspaces/{workspace_id}/cherry-pick \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "ref_id": "<string>"
}
'

202

{
  "merge_id": "example_id"
}

Authorizations

Authorization · string · header · required

This API uses OAuth 2 with the implicit grant flow

Path Parameters

repo_id · string · required

The repo ID of the repository. Repo name can be used instead of the ID, but usage of ID for permanent linking and API requests is preferred.

Required string length: 3 - 128

Example:

"example_id"

workspace_id · string · required

The repo ID of the workspace.

Required string length: 3 - 128

Example:

"example_id"

Body

application/json

ref_id · string · required

The commit to cherry-pick

Required string length: 7 - 128

Response

202

application/json

The cherry-pick is in progress. It has conflicts requiring active input from the user for conflict resolution. The response contains a merge ID, which can be used for querying /repos/{repo_id}/merges/{merge_id}

merge_id · string · required

Required string length: 3 - 128

Example:

"example_id"