From: Jeremy Morton Date: Fri, 09 Mar 2012 11:28:58 GMT Subject: Re: git push default behaviour? Message-ID: In-Reply-To: <7vipie85nk.fsf@alter.siamese.dyndns.org> On Fri, Mar 9, 2012 at 9:50 AM, Junio C Hamano wrote: > Matthieu Moy writes: > >> And regardless of the danger, if I look around me, I see almost only >> people working with shared archives, and a few projects (including Git, >> obviously) using the "one commiter per repository" workflow (I teach Git > > These days, you do not have to even go to kernel.org to find people > and projects that use "publish to be pulled" model.  I hear that > there is a popular site called GitHub where people create their own > fork, publish their work there and ask the project they forked from > to pull their work. Github also offer a paid service where you can host private repositories, which you're probably going to work on as part of a team in a business. FWIW, I discovered the problem with this default behaviour because someone accidentally did a 'git push --force' to our github repo. There is currently no hook mechanism with github that allows you to abort a push, either, so you can't stop the problem that way. Best regards, Jeremy Morton (Jez)