in case of ff-merges, the incarnation status might return the result of a wrong pipeline

[defreng]

if an update to an incarnation is merged with fast-forward merges, the gitlab commit status API might return the status of the pipeline that was running as part of the merge-request, instead of the one running on the main branch.

See the following example commit API response:

{
  "id": "b29e2d1763d03119f6c3c6514355b2c9c822fa3c",
  "short_id": "b29e2d17",
  "status": "success",
  "last_pipeline": {
    "iid": 1,
    "sha": "b29e2d1763d03119f6c3c6514355b2c9c822fa3c",
    "ref": "foxops/initialize-to-3a52ce7-v7.55.0",
  }
  [...]
}

See the ref in last_pipeline (although this commit was already merged to main branch)