ResolveConflictsPreview
What resolving would do, without doing it — ?dry_run=true.
Shape
- allowedboolean
pipelinesarray of PredictedPipelineThe pipelines the merge commit would start on the merge request's branch.
- The PredictedPipeline schema
- namestring
- pipeline_idPipelineId (string · uuid) or nulloptionalThe pipeline, when it is one stored in the platform. A pipeline declared in a file under
.gitmoap/pipelines/has no id and is named by its file.
refusalsarray of Refusal
- The Refusal schema
- codeRefusalCodePERMISSION_REQUIREDBRANCH_PROTECTEDAGENT_REFFOREIGN_AUTHORPRIVILEGED_PATHBRANCH_NOT_FOUNDSTART_BRANCH_NOT_FOUNDFILE_NOT_FOUNDREPOSITORY_EMPTYMR_NOT_OPENNOT_CONFLICTEDHEAD_MOVEDBRANCH_EXISTSFILE_CHANGEDFILE_EXISTSPATH_CONFLICTUNSUPPORTED_ENTRYNOTHING_TO_COMMITUNRESOLVEDNOT_IN_CONFLICTUNSUPPORTED_CONFLICTPUSH_RULE_VIOLATIONWhat kind of refusal this is. Closed: a client branches on it. The wire spelling is the
SCREAMING_SNAKEdomain code that leads an error's message, so a refusal returned as data and the same refusal returned as an error read the same. - messagestringWhat is wrong, in a sentence a person can act on.
- fieldstring or nulloptionalThe part of the request the refusal is about:
message,branch, oractions[i]for the i-th file change. - rulestring or nulloptionalThe push rule that refused, by its setting's name (
require_issue_reference), whencodeisPUSH_RULE_VIOLATION.
Example
Synthesized example{
"allowed": false,
"pipelines": [
{
"name": "payments-api"
},
{
"name": "payments-api"
}
],
"refusals": [
{
"code": "PERMISSION_REQUIRED",
"message": "Draw the region map from operation density"
},
{
"code": "PERMISSION_REQUIRED",
"message": "Stream pipeline status into the run header"
}
]
}
Graph
Used inside
No schema contains this one.
Contains
Used by
Sent by 0 operations
No operation takes it as a request body.
Returned by 1 operation