So you imported your GitHub repo to GitLab as you migrate to GitLab, but you still want to ensure everything is in-sync while you doing work on other parts such as migrating GitHub Actions workflows to either use GitLab CI format in only Docker containers or set up act stuff and even copying issue and PR templates to .gitlab directory.[^1]
The problem here is while you migrate to GitLab you also need to deal with contributors who didn't know that you're in the progress of moving to GitLab.
Possible workarounds/solutions
Set up bidirectional webhooks stuff and cross your fingers everything is fine.
Prompt the user to take the issue to the GitLab project, close, and lock it down.
An much better approach is to copy the issue title, description, and labels to GitLab, provide them the link, close and lock it down.
[^1]: While this might be related to Microsoft's acquisition of GitHub years ago, that is not factored in here.
About this Idea
So you imported your GitHub repo to GitLab as you migrate to GitLab, but you still want to ensure everything is in-sync while you doing work on other parts such as migrating GitHub Actions workflows to either use GitLab CI format in only Docker containers or set up
act
stuff and even copying issue and PR templates to.gitlab
directory.[^1]The problem here is while you migrate to GitLab you also need to deal with contributors who didn't know that you're in the progress of moving to GitLab.
Possible workarounds/solutions
[^1]: While this might be related to Microsoft's acquisition of GitHub years ago, that is not factored in here.