Serve several projects: route a report to its project's repository #8

New issue

Open

opened 2026-10-28 00:15:52 +00:00 by laurence · 0 comments

laurence commented

2026-10-28 00:15:52 +00:00

Owner

Part of the parity work (valerian#217): Valerian and Annora get the same in-app feedback as Helia.

The relay files every report into one repository (FEEDBACK_REPO, laurence/helia). Valerian and Annora need their reports in their own issue lists, through the same relay and the same bot.

Wanted: an optional project member on the report and a FEEDBACK_PROJECTS setting (valerian=laurence/valerian,annora=laurence/annora) that maps it to a repository. A report without project still goes to Helia, so older clients keep working. A project the relay does not serve is refused (unknown_project), so a client cannot choose an arbitrary repository.

Deployment (owner/ops, not part of the code change): the helia-feedback bot needs issue access to each added repository, and the stack's environment gets FEEDBACK_PROJECTS. Each repository also needs the labelling workflow (feedback-labels.yml) because the bot cannot set labels.

Acceptance criteria

project parsed and validated; FEEDBACK_PROJECTS parsed and validated (names a-z 0-9 -, helia is the default and cannot be listed).
The report, labels, screenshot upload and body update go to the project's repository; the health probe checks every repository.
End-to-end test with two mock repositories; protocol page and README updated.

Part of the parity work (valerian#217): Valerian and Annora get the same in-app feedback as Helia. The relay files every report into one repository (`FEEDBACK_REPO`, `laurence/helia`). Valerian and Annora need their reports in their own issue lists, through the same relay and the same bot. **Wanted:** an optional `project` member on the report and a `FEEDBACK_PROJECTS` setting (`valerian=laurence/valerian,annora=laurence/annora`) that maps it to a repository. A report without `project` still goes to Helia, so older clients keep working. A project the relay does not serve is refused (`unknown_project`), so a client cannot choose an arbitrary repository. **Deployment (owner/ops, not part of the code change):** the `helia-feedback` bot needs issue access to each added repository, and the stack's environment gets `FEEDBACK_PROJECTS`. Each repository also needs the labelling workflow (`feedback-labels.yml`) because the bot cannot set labels. **Acceptance criteria** - [ ] `project` parsed and validated; `FEEDBACK_PROJECTS` parsed and validated (names a-z 0-9 -, `helia` is the default and cannot be listed). - [ ] The report, labels, screenshot upload and body update go to the project's repository; the health probe checks every repository. - [ ] End-to-end test with two mock repositories; protocol page and README updated.

laurence added the

labels

2026-10-28 00:15:52 +00:00

laurence referenced this issue from a commit

2026-10-28 00:16:01 +00:00

Serve several projects: route a report to its project's repository (#8)

laurence referenced this issue from a pull request that will close it,