#5103 web interface behaves strange for git repository without master branch [ss954]

v1.0.0
closed
nobody
support (446) p3 (267) 42cc (432)
SCM
Tim Van Steenburgh
2015-08-20
2012-10-10
Chris Tsai
No

[forge:site-support:#954]

See: https://sourceforge.net/p/alleg/allegro/

They don't have the standard "master", perhaps we need a config option to set a default branch in the absence of a "master" branch?

The web interface thinks the project is empty. Maybe you can add a way to detect or set the default branch, like on github?

Related

Tickets: #5103

Discussion

  • Chris Tsai - 2012-11-27

    Report of similar case for hg: [forge:site-support:#1704]

    https://sourceforge.net/p/anuchem/code/

     

  • Chris Tsai - 2013-02-20

    [forge:site-support:#2850]

    More hg examples here: https://sourceforge.net/p/evilnet/_list/hg (as of writing, all but "nefarious2")

     

  • Dave Brondsema

    Dave Brondsema - 2013-06-11
    • labels: support, p3 --> support, p3, 42cc
    • Milestone: limbo --> forge-backlog
     

  • Dave Brondsema

    Dave Brondsema - 2013-06-11

    Let's add an admin option to specify a default branch, for git & hg. If set, use that instead of hard-coded "master" whenever appropriate.

     

  • Igor Bondarenko - 2013-06-12

    Created #374: [#5103] admin option to specify default branch for git and hg (2cp)

     

    Related

    Tickets: #5103

  • Igor Bondarenko - 2013-06-12
    • status: open --> in-progress
     

  • Igor Bondarenko - 2013-06-20
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-06-20

    Closed #374.

    Allura: je/42cc_5103
    ForgeHg: 42cc_5103

     

  • Tim Van Steenburgh - 2013-06-27
    • QA: Tim Van Steenburgh
    • Milestone: forge-backlog --> forge-jun-28
     

  • Tim Van Steenburgh - 2013-06-28
    • status: code-review --> in-progress
     

  • Tim Van Steenburgh - 2013-06-28

    The code for setting the branch name works fine. But the repo tree view still appears empty. Here are the steps to replicate, see if this works for you:

    • Create new Git tool and set default branch to 'mybranch'
    • Clone to filesystem
    • touch file1 && git add . && git commit -m "1"
    • git checkout -b mybranch && touch file2 && git add . && git commit -m "2"
    • git push origin mybranch
    • After the refresh, mybranch does appear to be HEAD, but the repo still appears empty: http://screencast.com/t/EovbE2wBDUcl
     

  • Dave Brondsema

    Dave Brondsema - 2013-06-28
    • Milestone: forge-jun-28 --> forge-jul-12
     

  • Igor Bondarenko - 2013-07-01

    Created #396: [#5103] Repo is empty on default branch (2cp)

    I was able to reproduce this too. We'll investigate in the #396.

     

    Related

    Tickets: #5103

  • Igor Bondarenko - 2013-07-04
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-07-04

    Closed #396.

    Allura: je/42cc_5103 (forced update)
    ForgeHg: 42cc_5103

     

  • Tim Van Steenburgh - 2013-07-07
    • status: code-review --> blocked
     

  • Tim Van Steenburgh - 2013-07-07

    Both branches merged to master. Once the new ForgeHg build hits python tree (https://trac.sdot.me/trac/siteops/ticket/54029), need to bump version on Allura.

     

  • Tim Van Steenburgh - 2013-07-07
    • status: blocked --> closed
     

  • Tim Van Steenburgh - 2013-07-07

    ForgeHg version will be bumped by [#3060].

     

    Related

    Tickets: #3060

Log in to post a comment.