I self-host Multica and map projects to GitHub repos through config files on my end, then run a bash script that loops through gh issue list and multica issue create to backfill the board. It works for a one-time import but drifts immediately — if a PR gets merged or an issue gets closed on GitHub, the Multica issue just sits there until I go clean it up manually. A lightweight sync that watches linked workspace repos and mirrors open issues/PRs as backlog items (creating, closing, maybe updating status when things get merged) would replace all this glue code and keep the board honest without babysitting it.
I self-host Multica and map projects to GitHub repos through config files on my end, then run a bash script that loops through
gh issue listandmultica issue createto backfill the board. It works for a one-time import but drifts immediately — if a PR gets merged or an issue gets closed on GitHub, the Multica issue just sits there until I go clean it up manually. A lightweight sync that watches linked workspace repos and mirrors open issues/PRs as backlog items (creating, closing, maybe updating status when things get merged) would replace all this glue code and keep the board honest without babysitting it.