[llvm-dev] RFC: Move the test-suite LLVM project to GitHub?

Joachim Durchholz via llvm-dev llvm-dev at lists.llvm.org
Wed Feb 24 14:01:40 PST 2016

Am 24.02.2016 um 21:57 schrieb Chandler Carruth via llvm-dev:
> For all of these reasons, and also because I'd like to see how well (or
> rather, how poorly) a service like GitHub actually works for the project,
> it seems like splitting the test-suite out of the current subversion
> repository and moving it there is the right call.

My experience from a few years of contributing and a bit of project setup:

#1) GitHub works really well for public discussions of code changes 
(pull requests) and issues.

#2) Labels are too roughly granular to be very useful. Don't expect to 
be doing request priorization etc. on that route. (This may change in 
the future.)

#3) Contributors without commit rights need to set up a fork (really a 
"git clone") on GitHub, and commit to that before they can issue a pull 
This sounds easy enough in theory, but for your local work you pull and 
merge from "origin" and push to "fork", and then you go to the GH site 
and start the pull request, and once it's in you start cleaning up work 
branches both locally and on GitHub. It's a lot of clerical work, and 
some aspects of this all are easy to get wrong for a git newbie.

I found that GitLab does #3 much better.
People can push their work branches directly to the project repo. You 
can set up the master branch (or any other branch) to require committer 
rights, so you can protect the master branch and don't have to force 
contributors into their own repositories.
The rest is roughly on par with GitHub. GitLab isn't as polished in all 

Oh, and the GitLab server-side code is available as Open Source. So if 
you want to set up your own servers, you can do that.
GitHub did not open source their server code. If Github goes down, the 
projects need to migrate to a different git hoster.

> There is still plenty to figure out about how to manage this on github, but
> before doing anything else I just wanted to shoot an email and see if folks
> like this idea.

Feel free to ask, I have been through some of the setup pain.


More information about the llvm-dev mailing list