Merge a pull request marked ready at its head once its checks pass (issue 722)

The operator wants a reviewed pull request merged without a session calling the merge tool again after every recheck. The reviewer marks it ready (label mesh/ready and a comment "ready at <full head sha>"); the forge's open-pulls read carries the mark, and mesh-delivery merges through gitea_merge_pull_request at that head, in a group's order once its composed check passed. A push after the mark clears it; a failed check is said on the pull request and as a stalled line.
2026-10-14 21:23:26 +02:00
parent 482232e8c5
commit 7e0001e304
15 changed files with 688 additions and 10 deletions
@@ -514,7 +514,7 @@ function allGiteaTools(gitea: GiteaClient): ToolDefinition[] {
    },
    {
      name: "gitea_open_pulls",
-      description: "Every open pull request of every repository, from the forge itself: its head, its base, the statuses the base's protection requires and the ones its head has, each with its state, description and when it was set. What mesh-delivery reads to say a pull request the mesh was never asked to check (novox/hq issue 347), or whose check started and never answered (issue 438). Reads only.",
+      description: "Every open pull request of every repository, from the forge itself: its head, its base, the statuses the base's protection requires and the ones its head has, each with its state, description and when it was set. What mesh-delivery reads to say a pull request the mesh was never asked to check (novox/hq issue 347), or whose check started and never answered (issue 438), and each pull request's labels and ready mark — the label mesh/ready and the head the newest comment \"ready at <full head sha>\" names — which mesh-delivery merges on (issue 722). Reads only.",
      input: {},
      run: async () => ({ pulls: await gitea.openPulls() }),
    },