The importer records a literal gitmsg/social for posts and comments (library/import/import.go), although social's branch is the workspace's own setting. Check which branch it commits to before calling it a bug; fix the recorded branch if they differ.
↩ Max Rakhimov · 2026-09-28
Fixed on main by #commit:56fe0a2c0e01: both social Record calls carry the branch the commits landed on; verified end to end with a configured non-default social branch. The review confirmed the mapping's Branch is metadata nothing reads back today, so the bug was latent, and found no issues.