Back in 2016 @hellokittyasked a question about obtaining DOIs for GitLab repos, so that people can easily cite the contents for a repo.
This is easily done in GitHub with Zenogo integrations, and there has been somediscussion of this on the issues lists.
Does anyone have a workaround for this, maybe using webhooks? Or do people manually upload tarballs whenever they make a release? It would be really nice to have an automated recipe that could go in a .gitlab-ci.yml…
Thanks for answering and providing the information.
I feel it is a really relevant missing feature, giving GitHub a strong competitive advantage.
Do you agree?
Do you have any suggestions on how to proceed to stimulate the development of an easy way to provide a GitLab project with a DOI?
The usual way to encourage GitLab to implement a particular feature is to up-vote (and maybe comment on) the relevant issues. This is how GitLab measures customer demand (outside of talking directly to sales people).
Please do up-vote the ones I linked to, and if you have colleagues working in the same area, please encourage them to do the same.