Get merge request conflicts
Returns the list of conflicting configurations between the source (dev) branch and the target (default) branch of the merge request. A conflict means the merge cannot proceed without resolving it (for example, the configuration was changed in both the dev branch and the default branch since the dev branch last took it from the default branch, i.e. branch creation, rebase or reset to default; in projects with a protected default branch any change in the default branch counts).
The endpoint is primarily intended for UI consumption — callers can detect conflicts before attempting a merge. An empty array means the merge request can be merged without conflicts.
Request
- Base URLhttps://connection.keboola.com
- Auth
- API key in header X-StorageApi-Token
- or API key in header X-KBC-ManageApiToken
- or HTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Response
List of merge conflicts between the dev and default branch. Empty array means no conflicts.
Changes
No recorded changes to this operation across all 1 revision of this API.