Mark reports processed after publishing #15

Closed
opened 2026-07-02 17:44:35 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-07-02 17:44:35 +00:00 (Migrated from github.com)

Context

Completes the weekly job from JMR-dev/LibreMail#35: processed reports must not be re-published on the next run.

Scope

  • After a report is successfully published as a GitHub issue (#14), transition its status to published via #10's lifecycle model.
  • Handle partial failures: if publishing issue N fails, reports 1..N-1 already marked published stay published, and N is retried on the next run rather than silently dropped or duplicated.

Acceptance criteria

  • After a full run, all successfully published reports show published status; a report that failed to publish remains pending and is retried next run without duplicating already-published ones.

Dependencies

Depends on #10 (lifecycle model) and #14 (publish step).

## Context Completes the weekly job from [JMR-dev/LibreMail#35](https://github.com/JMR-dev/LibreMail/issues/35): processed reports must not be re-published on the next run. ## Scope - [ ] After a report is successfully published as a GitHub issue (#14), transition its status to `published` via #10's lifecycle model. - [ ] Handle partial failures: if publishing issue N fails, reports 1..N-1 already marked published stay published, and N is retried on the next run rather than silently dropped or duplicated. ## Acceptance criteria - After a full run, all successfully published reports show `published` status; a report that failed to publish remains `pending` and is retried next run without duplicating already-published ones. ## Dependencies Depends on #10 (lifecycle model) and #14 (publish step).
Sign in to join this conversation.