Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
This tool is a fantastic resource, but it is only accessible to users of GitHub. Our Centre uses a self-hosted instance of GitLab rather than GitHub. This is preferable for issues around protecting IP, and open source principles.
I have been able to fork a GitHub workshop built using this tool into GitLab, but there is (I'm sure) functionality under the hood which is not developed for GitLab.
Describe the solution you'd like
I would like for equivalent feature support to be available to users of GitLab as it is to users of GitHub.
Describe alternatives you've considered
We are currently woking around this issue by creating the complete and functioning workshop on GitHub and then forking the final version to GitLab. Thanks to @mjaquiery for this suggestion. This is suboptimal as we are picking up integration issues as we find them, rather than fully benefitting from the excellent development work which has already gone into the project.
Additional context
If GitLab integration was fully supported, we would be well incentivised to efficiently roll out this tool to deliver all of the reproducibility training we are creating for the Centre (more details on our plans here).
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
This tool is a fantastic resource, but it is only accessible to users of GitHub. Our Centre uses a self-hosted instance of GitLab rather than GitHub. This is preferable for issues around protecting IP, and open source principles.
I have been able to fork a GitHub workshop built using this tool into GitLab, but there is (I'm sure) functionality under the hood which is not developed for GitLab.
Describe the solution you'd like
I would like for equivalent feature support to be available to users of GitLab as it is to users of GitHub.
Describe alternatives you've considered
We are currently woking around this issue by creating the complete and functioning workshop on GitHub and then forking the final version to GitLab. Thanks to @mjaquiery for this suggestion. This is suboptimal as we are picking up integration issues as we find them, rather than fully benefitting from the excellent development work which has already gone into the project.
Additional context
If GitLab integration was fully supported, we would be well incentivised to efficiently roll out this tool to deliver all of the reproducibility training we are creating for the Centre (more details on our plans here).