(Preview) Resolve Git conflicts
post
/20260430/aiDataPlatforms/{aiDataPlatformId}/workspaces/{workspaceKey}/gitRepositories/{gitRepositoryKey}/actions/resolveConflicts
(Preview) Synchronously selects LOCAL or REMOTE file versions, or stages
manually resolved content with MARK_RESOLVED. Does not complete or push an
in-progress merge or rebase.
Request
Path Parameters
-
aiDataPlatformId(required): string
Minimum Length:
1Maximum Length:500The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the AI Data Platform (Data Lake) instance. -
gitRepositoryKey(required): string
Minimum Length:
1Maximum Length:200The opaque repository key, available as GitRepository.key or system:repoKey in the folder's JSON file-metadata HEAD response header when shouldIncludeMetadata=true. Distinct from the async operation resourceName. -
workspaceKey(required): string
Minimum Length:
1Maximum Length:200The key of the Workspace
Header Parameters
-
if-match: string
Maximum Length:
1000For optimistic concurrency control. In the PUT or DELETE call for a resource, set the `if-match` parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value. -
opc-request-id: string
Maximum Length:
255Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash. -
opc-retry-token: string
Maximum Length:
64A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected.
Conflict resolution details.
Root Schema : ConflictResolveDetails
Type:
objectFile paths and resolution action for a Git conflict resolution request.
Show Source
-
action(required):
string
Allowed Values:
[ "LOCAL", "REMOTE", "MARK_RESOLVED" ]LOCAL selects the local version and REMOTE selects the incoming version, with Git side mapping adjusted during rebase. MARK_RESOLVED stages manually resolved workspace content. -
files(required):
array files
Minimum Number of Items:
1Maximum Number of Items:100Repository-relative paths of the conflicted files to resolve or stage.
Nested Schema : files
Type:
arrayMinimum Number of Items:
1Maximum Number of Items:
100Repository-relative paths of the conflicted files to resolve or stage.
Show Source
-
Array of:
string
Minimum Length:
1Maximum Length:10000
Response
Supported Media Types
- application/json
200 Response
Selected files were resolved and staged.
Headers
-
etag: string
For optimistic concurrency control. See `if-match`.
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : GitBranch
Type:
objectGit branch details.
Show Source
-
branchName(required):
string
The name of the Git branch.
-
errorMessage:
string
Git error message.
-
gitExitCode:
integer
Git exit status.
-
gitUrl(required):
string
The Git repository URL corresponding to the branch.
-
stdErr:
string
Git STDERR message.
-
stdOut:
string
Git STDOUT message.
400 Response
Bad Request (invalid query parameters, malformed headers, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
401 Response
Unauthorized (missing or expired credentials, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
404 Response
Not Found. The requested resource was not found.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
409 Response
Conflict. Request conflicts with the current state of the resource.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
412 Response
Precondition Failed (One or more conditions in request failed).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
429 Response
Too Many Requests. Too many requests sent to the server in a short period.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
500 Response
Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
Default Response
Unknown Error. Error is not recognized by the system.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.