feat: support importing patch sources from more forges #14

New issue

reseam-bot · 2026-10-15T02:30:11Z

reseam-bot commented

2026-10-15 02:30:11 +00:00

Feature description

Support adding patch sources from repository links hosted on more forges, not just the formats currently recognized by the manager. At minimum, document and test repository/release links for GitHub, GitLab, Forgejo and Gitea, and make the supported forge URL patterns extensible.

When a user pastes a repository URL, the manager should locate the latest compatible Reseam bundle or publisher index in that repository's releases and give a clear error if the forge or release layout is unsupported. In particular, the current generic 'made for an older version' message should not imply a bundle compatibility problem when the actual issue is an unsupported source URL.

Motivation

A user tried adding https://github.com/madkarmaa/reseam-patches from the Add patch source screen and got an error. Patch authors host their sources on different forges, and users reasonably expect a repository link to work without having to find and paste a release asset URL manually.

Acceptance criteria

Recognize repository URLs for the supported forges and resolve the expected release asset/index URL.
Support the documented release layouts (including a .reseam bundle and/or patches.json index, as applicable).
Add tests for repository URL parsing and release asset lookup, including failure cases for unsupported or missing assets.
Show a useful error that distinguishes an unsupported forge/layout from an incompatible bundle version.

Source: https://discord.com/channels/1495093872261599323/1556366364053213315/1560116734130782271

### Feature description Support adding patch sources from repository links hosted on more forges, not just the formats currently recognized by the manager. At minimum, document and test repository/release links for GitHub, GitLab, Forgejo and Gitea, and make the supported forge URL patterns extensible. When a user pastes a repository URL, the manager should locate the latest compatible Reseam bundle or publisher index in that repository's releases and give a clear error if the forge or release layout is unsupported. In particular, the current generic 'made for an older version' message should not imply a bundle compatibility problem when the actual issue is an unsupported source URL. ### Motivation A user tried adding `https://github.com/madkarmaa/reseam-patches` from the Add patch source screen and got an error. Patch authors host their sources on different forges, and users reasonably expect a repository link to work without having to find and paste a release asset URL manually. ### Acceptance criteria - Recognize repository URLs for the supported forges and resolve the expected release asset/index URL. - Support the documented release layouts (including a `.reseam` bundle and/or `patches.json` index, as applicable). - Add tests for repository URL parsing and release asset lookup, including failure cases for unsupported or missing assets. - Show a useful error that distinguishes an unsupported forge/layout from an incompatible bundle version. Source: https://discord.com/channels/1495093872261599323/1556366364053213315/1560116734130782271

Sign in to join this conversation.

No labels

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

reseam/manager#14

Rows
Columns