Merge Requests

A merge request is how you propose and review changes from one branch before they land in another. It gives your team a chance to see exactly what changed, catch any conflicts, and approve the work before it becomes part of the main product model.

Creating a merge request

1. Go to the Branches view (left sidebar)
2. Find the branch you want to merge
3. Click the Merge Request button (or the three-dot menu → Open merge request)
4. Choose the target branch — typically main
5. Give the merge request a title and optional description
6. Click Create merge request

The merge request opens immediately in the Merge Requests view.

The merge request view

The merge request view has two tabs:

Diff tab

Shows everything that changed on your branch compared to the target:

• Added nodes — new domains, capabilities, features, etc.
• Removed nodes — nodes that were deleted
• Updated fields — field-level changes with before/after values
• Changed relationships — new or removed connections between nodes

Use the diff to review the full scope of the change before merging.

Conflicts tab

Specor automatically detects conflicts — situations where both branches changed the same node in incompatible ways. The Conflicts tab lists every conflict that must be resolved before the merge can go through.

Resolving conflicts

For each conflicting node, Specor shows you both versions side-by-side:

• The branch version (the changes you’re merging in)
• The main version (what’s currently on the target branch)

You have three options for each conflict:

Option	What it does
Keep branch version	Use the version from the branch being merged
Keep main version	Keep the existing version, discard the branch’s changes
Edit	Open the node editor to write a combined version manually

Once every conflict is resolved, the Merge button becomes available.

Merging

Click Merge to complete the merge. Specor will:

1. Apply all non-conflicting changes from the branch
2. Apply your conflict resolutions
3. Create a new commit on the target branch recording the merge
4. Mark the merge request as merged

The branch remains intact after merging — it isn’t deleted automatically. You can archive it from the Branches view.

Closing without merging

To discard a merge request without merging:

• Click Close merge request from the merge request detail page

The merge request is closed but the branch is unaffected. You can open a new one later if needed.

Tips

• Merge often. Long-lived branches accumulate more conflicts. Frequent small merges are easier to review.
• Write good descriptions. Other reviewers (and your future self) will appreciate context on why the changes were made.
• Preview first. You can compare any two branches from the Diff view before formally opening a merge request.