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

Joachim Durchholz via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 25 04:49:58 PST 2016

Am 25.02.2016 um 13:08 schrieb Tony Kelman via llvm-dev:
> Mehdi Amini via llvm-dev <llvm-dev <at> lists.llvm.org> writes:
>>> This is a little more complex. SVN is very conservative on history,
>>> and that saves us from destroying the origin. Git, on the other hand,
>>> allows anyone with write access to completely wipe out the repo. I
>>> don't think anyone would want to, but accidents do happen in git.
>> This is why git has "hooks": for example
> https://gist.github.com/stefansundin/d465f1e331fc5c632088
>> You can prevent from rewriting the history on the server side, which
> eliminate risk of "accidents". (You
>> can have a whitelist of people allowed to rewrite the history...).
> One downside of hooks is that you're relying on everyone who has commit
> access to manually set them up on every machine they might commit from.

If the repo is on GitHub, the hook runs on GitHub, so individual 
committers don't have to do anything specific.

> On the server side, GitHub has a relatively recent feature called
> protected branches that you can enable
> (https://github.com/blog/2051-protected-branches-and-required-status-checks)
> to prevent force pushing
> to important permanent branches like master or releases.

Oh, I wasn't aware that they added this.
That fixes my biggest reservation about GitHub.

More information about the llvm-dev mailing list