madt_issues import: accept owner_repo for parity with create/deps_add #351

New issue

Closed

opened 2026-07-22 20:44:17 +00:00 by hexajon · 0 comments

hexajon commented

2026-07-22 20:44:17 +00:00

(Migrated from codeberg.org)

madt_issues action=import only targets the server's launch-cwd repo - it takes no owner_repo= (or dir=), so I can't bulk-import a roadmap into another repo on the same forge without cd-ing a session into it.

Its own building blocks already can: create and deps_add both accept owner_repo=, and I routinely file a whole epic + dependency graph into another repo that way, one call at a time. import is just those batched with topo ordering - there's no reason it can't take the same owner_repo=.

Ask: give import an owner_repo= param, resolved the same way create/deps_add resolve it (launch credential against the named repo on the same forge).

The boundary I'm not asking to cross: dir=-style bulk import (borrowing a foreign checkout's token for bulk writes) should stay refused - that's the credential-boundary blast radius. This is only about the owner_repo= same-forge dispatch the per-issue actions already allow.

`madt_issues action=import` only targets the server's launch-cwd repo - it takes no `owner_repo=` (or `dir=`), so I can't bulk-import a roadmap into another repo on the same forge without cd-ing a session into it. Its own building blocks already can: `create` and `deps_add` both accept `owner_repo=`, and I routinely file a whole epic + dependency graph into another repo that way, one call at a time. `import` is just those batched with topo ordering - there's no reason it can't take the same `owner_repo=`. Ask: give `import` an `owner_repo=` param, resolved the same way `create`/`deps_add` resolve it (launch credential against the named repo on the same forge). The boundary I'm *not* asking to cross: `dir=`-style bulk import (borrowing a foreign checkout's token for bulk writes) should stay refused - that's the credential-boundary blast radius. This is only about the `owner_repo=` same-forge dispatch the per-issue actions already allow.

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

sixfold-space/madtea#351

No description provided.

Rows
Columns