From cc62a9ddf6edd383ff4efccba676e9e3cc50daa4 Mon Sep 17 00:00:00 2001 From: Hardik Date: Thu, 11 Jun 2026 17:05:52 +0530 Subject: [PATCH] docs(automation): note Forgejo 10 broken-PR quirk and close/reopen fix Co-Authored-By: Claude Fable 5 --- automation/README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/automation/README.md b/automation/README.md index 058a424..264a7a0 100644 --- a/automation/README.md +++ b/automation/README.md @@ -67,3 +67,17 @@ The runner deploys the tag and restarts the app. Watch progress under `docker exec -u 1000 forgejo forgejo admin user generate-access-token ...`. - Server-side env for the button lives in `~/pms/App/.env` on pms1 (`FORGEJO_URL=http://127.0.0.1:3001` so it does not depend on the tunnel). +- **Known Forgejo 10 bug:** clicking *Update branch* on a PR (or pushing to its + head branch) can make the page show "This pull request is broken due to + missing fork information" even though the PR is fine (API still reports + `mergeable: true`). Fix: close and reopen the PR — via the UI, or: + + ```powershell + $h = @{ Authorization = "token " } + Invoke-RestMethod -Method Patch -Headers $h -ContentType application/json ` + -Uri https://git.pelagiamarine.com/api/v1/repos/shad0w/pelagia-portal/pulls/ -Body '{"state":"closed"}' + Invoke-RestMethod -Method Patch -Headers $h -ContentType application/json ` + -Uri https://git.pelagiamarine.com/api/v1/repos/shad0w/pelagia-portal/pulls/ -Body '{"state":"open"}' + ``` + + Fixed upstream in newer Gitea/Forgejo — resolves itself if Forgejo is upgraded past v10.