Git and not rebasing branches pushed remotely ?

[Ian Young]

> On 25 Sep 2015, at 22:03, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> 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.

Not sure that's actually true (gitweb has some limitations, and I think one of them is that repositories are all in the same directory). I'd argue against this as a general practice even if it was possible, as mentioned in an earlier post.

> 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.

It's very common practice in Git-based development to also allow feature branches, particularly for features which are in flight for a long time. We probably want to think a bit and establish some ground rules before getting into that wholesale, but I don't see a reason to disallow one of the big advantages of the technology. I also certainly wouldn't push people into making feature/topic branches before they feel confident about how they work, and the personal repositories are a good way to gain that confidence.

    -- Ian




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5250 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/dev/attachments/20150926/36391992/attachment.p7s>