Cascade done status to issues when their closing PR merges #31

Closed
opened 2026-09-05 09:48:13 +08:00 by Breadway · 0 comments
Owner

User feedback: "when a PR is merged, it should be moved into the DONE column, no?" The PR itself already correctly flips to done on merge (existing map_status logic), but the issue(s) it closes didn't — and Forgejo itself only reliably auto-closes the first issue in a comma-separated "Closes #a, #b" list (confirmed repeatedly this session), so relying on Forgejo's own auto-close isn't enough. When a synced PR transitions to done, every issue in its closes links now cascades to done too, with a best-effort close of that issue's own Forgejo counterpart.

User feedback: "when a PR is merged, it should be moved into the DONE column, no?" The PR itself already correctly flips to done on merge (existing map_status logic), but the issue(s) it closes didn't — and Forgejo itself only reliably auto-closes the first issue in a comma-separated "Closes #a, #b" list (confirmed repeatedly this session), so relying on Forgejo's own auto-close isn't enough. When a synced PR transitions to done, every issue in its closes links now cascades to done too, with a best-effort close of that issue's own Forgejo counterpart.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadboard#31
No description provided.