Search friendliness.
Quite a few open-source projects rely heavily on being findable, and often use their Github README as a sort of "marketing site" for developers.
Finding projects organically on Gitlab is a nightmare.
Quite a few open-source projects rely heavily on being findable, and often use their Github README as a sort of "marketing site" for developers.
Finding projects organically on Gitlab is a nightmare.
I'm also convinced that the repo would be quite popular were it posted on Github because many related Pytorch repos on Github with far poorer code quality and documentation have 1000+ stars. As much as I love Gitlab, it is very hard for me to use anything but Github when working on an Open Source Project that I want to get lots of eyeballs on and hopefully the satisfaction of having other users use my code.
This of course won't benefit Gitlab's SEO in the long run, but it does allow using Gitlab with less of the cons.
The file name search is pretty rapid though.
There's also a dedicated Search team being built at the moment to focus just on this.
Gitlab is one of the few products where I look forward to each release. You guys are doing a great job at keeping interest high and your communication is great.
I've resorted to using google search and append site:github.com to my query.
I also cross reference people from Twitter if they seem smart. And I click back and forth between NPM pages and GitHub pages to see people’s work.
Some of that is pretty doable if they switched to Gitlab... except the Twitter cross reference, just because I would have to remember to search both gitlab and GitHub.
This seemingly simple action does not work on Gitlab.
To answer your question, I do the above often on Github. Probably found projects that way as recently as last week.