Why it matters
Merge from anywhere gives ForkMesh a concrete mechanism for safe merge actions available from the branch, PR, or agent session flow. Merge from the desktop client with the branch view, the PR view, or straight from an agent's completed session.
Review becomes risky when merge state, discussion, and final application are trapped in a central service. In ForkMesh, merge from anywhere addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles merge from anywhere through the same split it uses across the product: ForkMesh derives diffs from live branches or signed patches, checks mergeability against the live base, and records review activity as portable data.
The behavior is intentionally narrow: Merge from the desktop client with the branch view, the PR view, or straight from an agent's completed session. Maintainers can verify what changed, who proposed it, and whether it will merge before touching the base branch.
Where it fits
Use merge from anywhere when contributors need familiar review mechanics without making one hosted PR database the source of truth.
It pairs with the rest of Pull requests & review because Merge from anywhere keeps safe merge actions available from the branch, PR, or agent session flow connected to the repository, its signatures, and the nodes that serve it.