Why it matters
Real mergeability checks gives ForkMesh a concrete mechanism for true three-way merge checks against the live base branch. Every PR is checked with a true three-way merge against the live base branch, so "can merge" means it will actually merge.
Review becomes risky when merge state, discussion, and final application are trapped in a central service. In ForkMesh, real mergeability checks 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 real mergeability checks 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: Every PR is checked with a true three-way merge against the live base branch, so "can merge" means it will actually merge. Maintainers can verify what changed, who proposed it, and whether it will merge before touching the base branch.
Where it fits
Use real mergeability checks 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 Real mergeability checks keeps true three-way merge checks against the live base branch connected to the repository, its signatures, and the nodes that serve it.