Git and not rebasing branches pushed remotely ?

Cantor, Scott cantor.2 at osu.edu
Fri Sep 25 17:03:15 EDT 2015


On 9/25/15, 3:39 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:

>My understanding was that “personal” (i.e. "name/project") repos are not visible via Gitweb.

They aren't now, that could obviously be changed if desired.

>And, if so, how do we make sure not to rebase branches pushed remotely ?

I only have the vaguest understanding of any of it, but I generally grasp why you don't want others working off a branch you might rebase.

I think publically speaking our branches are just meant for if we need to patch an older minor like we did with 3.1. If you need to make branches available for other purpose, they probably shouldn't be in the actual project repos, just pushed to a personal one. I don't think it matters whether gitweb can see that, does it? More whether somebody else could clone it locally for review.

-- Scott



More information about the dev mailing list