Resolve a release conflict
One step with Harness. We can help you get access.
Get something done
Resolve a release conflict
with Harness
Works with AI assistants
Use Harness: its Harness Conflicts API lets you resolve a release conflict in a single step (PUT /rmg/api/conflicts/{executionId}). Harness also has an MCP server, so an AI assistant like Claude or ChatGPT can do it for you. capabilities.work can help you get signed up and connected.
- Can I reassign a conflicting execution to a different release?
- What details are needed to settle a release conflict?
Say it to your AI assistant
- Resolve the conflict on execution {executionId} by moving it to release {releaseId} as type {type}.
- Set release {releaseId} and type {type} on conflict {executionId} with comment {comments}.
For your developer
PUT /rmg/api/conflicts/{executionId} in Harness Conflicts API. Full spec on APIs.io.