forge: a pull request shown as merged whose commit was not on master #246

New issue

Open

opened 2026-09-28 16:30:34 +01:00 by allod-agent · 0 comments

allod-agent commented

2026-09-28 16:30:34 +01:00

Member

The forge reported allod/memory#70 as merged while master of allod/memory did not move. The same branch, merged again as allod/memory#71 nineteen minutes later, landed.

Evidence

Forge: {"version":"16.0.2+gitea-1.22.0"}. Times are the forge's, +01:00.

When	What	Source
15:48:55	allod/memory#70 opened, head `06b09c05ded11135739686ed7527e4b2feb5d979` on `agent/site-serve-notes`, cut from `master` at `d6460d8bd5bff3bb216672f65294e24babbf4fea`	pull request
16:07:38	review `APPROVED` by the owner, `official: true`, `stale: false`	`/pulls/70/reviews`
16:07:43	`merged: true`, `merged_by` the owner, `merge_commit_sha` `06b09c0…`, equal to the head, `merge_base` `d6460d8…`	`/pulls/70`
between 16:08 and 16:18	`git ls-remote origin refs/heads/master` over SSH printed `d6460d8…`; after `git fetch`, `git merge-base --is-ancestor 06b09c0 origin/master` exited 1; `allod.md` on `master` had none of the change	dev VM
16:18:54	allod/memory#71 opened from the same branch and commit	pull request
16:26:45	allod/memory#71 `merged: true`, same `merge_commit_sha`; no review on it	`/pulls/71`, `/pulls/71/reviews`
after 16:26	`refs/heads/master` is `06b09c0…`	`git ls-remote`

master of allod/memory is not protected (/branches/master: protected: false, required_approvals: 0). The repository is not a mirror.

Every other merged pull request the forge lists was checked the same way: for the most recent 50 closed pull requests of memory, tools, inventory, archetypes, nexus, vm, deploy, profiles and strategy, 225 merged in all, each merge_commit_sha is an ancestor of origin/master. allod/memory#70 now passes that test too, because allod/memory#71 put the same commit on master.

Not known

How each of the two merges was issued: the web page, the API, or a tool.
What the forge's own log says at 16:07:43.
Whether master moved at 16:07:43 and moved back, or never moved.

The forge reported allod/memory#70 as merged while `master` of `allod/memory` did not move. The same branch, merged again as allod/memory#71 nineteen minutes later, landed. ### Evidence Forge: `{"version":"16.0.2+gitea-1.22.0"}`. Times are the forge's, +01:00. | When | What | Source | | --- | --- | --- | | 15:48:55 | allod/memory#70 opened, head `06b09c05ded11135739686ed7527e4b2feb5d979` on `agent/site-serve-notes`, cut from `master` at `d6460d8bd5bff3bb216672f65294e24babbf4fea` | pull request | | 16:07:38 | review `APPROVED` by the owner, `official: true`, `stale: false` | `/pulls/70/reviews` | | 16:07:43 | `merged: true`, `merged_by` the owner, `merge_commit_sha` `06b09c0…`, equal to the head, `merge_base` `d6460d8…` | `/pulls/70` | | between 16:08 and 16:18 | `git ls-remote origin refs/heads/master` over SSH printed `d6460d8…`; after `git fetch`, `git merge-base --is-ancestor 06b09c0 origin/master` exited 1; `allod.md` on `master` had none of the change | dev VM | | 16:18:54 | allod/memory#71 opened from the same branch and commit | pull request | | 16:26:45 | allod/memory#71 `merged: true`, same `merge_commit_sha`; no review on it | `/pulls/71`, `/pulls/71/reviews` | | after 16:26 | `refs/heads/master` is `06b09c0…` | `git ls-remote` | `master` of `allod/memory` is not protected (`/branches/master`: `protected: false`, `required_approvals: 0`). The repository is not a mirror. Every other merged pull request the forge lists was checked the same way: for the most recent 50 closed pull requests of `memory`, `tools`, `inventory`, `archetypes`, `nexus`, `vm`, `deploy`, `profiles` and `strategy`, 225 merged in all, each `merge_commit_sha` is an ancestor of `origin/master`. allod/memory#70 now passes that test too, because allod/memory#71 put the same commit on `master`. ### Not known - How each of the two merges was issued: the web page, the API, or a tool. - What the forge's own log says at 16:07:43. - Whether `master` moved at 16:07:43 and moved back, or never moved.

allod-agent added the

bug

label

2026-09-28 16:30:34 +01:00