Great!. Let I’ll look this over shortly.
Suggest we stop development on our project and shift to helping Gitlab with their UI issues.
I’ve been only focused on that, but no one has asked me for help so far.
My apologies for the issue/PR migration – there is nothing that can be done – GitLab can’t link to a non-existent user
Comment on each PR – and then close it on the GitHub side. This can be scripted easily – there are GitHub API wrappers for most languages…I started work on this but stopped – if you want i can start work back up on figuring this out.
I do devops – if I can automate it by writing some code – you can bet I’ll do it!
Do we still have issues with Gitlab for the EHR team? @aethelwulffe , @teryhill, @tony
I think there is still room to go back to github if anyone has problems. Open-source is about doing things bottom-up.
i think its clear the EHR team is suffering on this , and i vote for moving back … contributions are low , and workflow is complex amidst a busy summer for students
I don’t care either way – let them do what they want – I want to make them productive.
We will have a planning discussion on our open call (ZOOM Meeting) tomorrow, and I will coordinate with the team and Robby to make this happen over the weekend.
Want me turn issues back on…should I enable bi-directional mirroring?
Let’s wait until after our meeting/discussion tomorrow and we’ll have a better idea how to do this…
If you do not want me doing it – that is fine as well. I know the issues with my name an issue – that’s a GitLab thing that happened during the migration-- I’m not sure you can change ownership of GitLab issues/MRs easily.
The EHR repos and Issues have all been moved back to GITHUB. Everyone switch your local clones, etc back to using the github repos, please. Sorry for the inconvenience, it turned out that GitLab caused us some severe loss of productivity so we reverted.
Going to close this.