Post 883363 by fribbledom@mastodon.social
 (DIR) More posts by fribbledom@mastodon.social
 (DIR) Post #883363 by fribbledom@mastodon.social
       2018-10-31T17:05:27Z
       
       0 likes, 0 repeats
       
       You can finally move issues to different projects on GitHub. That must be all that Microsoft expertise at work.
       
 (DIR) Post #883449 by KitsuneAlicia@octodon.social
       2018-10-31T17:09:41Z
       
       0 likes, 0 repeats
       
       @fribbledom Wow! Forum mods moving threads to their correct subforums, but for git issue reports? I never would've thought of that!Good thing we have such smart people telling us what we can and can't do.
       
 (DIR) Post #883682 by 61@en.osm.town
       2018-10-31T17:23:28Z
       
       0 likes, 0 repeats
       
       @fribbledomOne of these days I will ยน come up with some #webhookery to move issues between #github and #GitLab, etc.ยน No I won't.
       
 (DIR) Post #883887 by fribbledom@mastodon.social
       2018-10-31T17:31:49Z
       
       0 likes, 0 repeats
       
       @61No need either way: GitLab's official importer already does that for you ๐Ÿ˜Š
       
 (DIR) Post #884352 by uvok@vulpine.club
       2018-10-31T17:59:33Z
       
       0 likes, 0 repeats
       
       @fribbledom as long as the Windows 10 1809 bug doesn't occur there... ๐Ÿ˜
       
 (DIR) Post #884856 by 61@en.osm.town
       2018-10-31T18:31:06Z
       
       0 likes, 0 repeats
       
       @fribbledomOnce, but what about projects that are distributed between the two hosts?Like say you have a project in #github and I have a dependency in #gitlab and someone files a bug against your project which turns out to be a problem on my component, so you transfer the bug report.
       
 (DIR) Post #887918 by fribbledom@mastodon.social
       2018-10-31T21:05:20Z
       
       0 likes, 0 repeats
       
       @61I hear you! I'm a huge proponent of a federated GitHub experience.