For each pending report from #13, decrypt (per #5's scheme) and format it into a GitHub issue body.
Create the issue in JMR-dev/LibreMail via the GitHub API, applying the label(s) decided in #6.
De-duplication: a report already published must not be re-published on a later run.
GitHub token stored as a Worker secret (Cloudflare Secret Manager), never committed.
Acceptance criteria
Given several pending reports, a run creates one well-formed, labeled GitHub issue per report; re-running does not duplicate any of them.
Dependencies
Depends on #5 (decrypt), #6 (labels), #13 (schedule + list).
## Context
Implements the publish step of [JMR-dev/LibreMail#35](https://github.com/JMR-dev/LibreMail/issues/35).
## Scope
- [ ] For each pending report from #13, decrypt (per #5's scheme) and format it into a GitHub issue body.
- [ ] Create the issue in `JMR-dev/LibreMail` via the GitHub API, applying the label(s) decided in #6.
- [ ] De-duplication: a report already published must not be re-published on a later run.
- [ ] GitHub token stored as a Worker secret (Cloudflare Secret Manager), never committed.
## Acceptance criteria
- Given several pending reports, a run creates one well-formed, labeled GitHub issue per report; re-running does not duplicate any of them.
## Dependencies
Depends on #5 (decrypt), #6 (labels), #13 (schedule + list).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
Implements the publish step of JMR-dev/LibreMail#35.
Scope
JMR-dev/LibreMailvia the GitHub API, applying the label(s) decided in #6.Acceptance criteria
Dependencies
Depends on #5 (decrypt), #6 (labels), #13 (schedule + list).