26 Jul, 2012

1 commit

  • …ore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
    Michael van Rooijen
     

18 Jul, 2012

1 commit


17 Jul, 2012

1 commit


16 Jul, 2012

1 commit


10 Jul, 2012

2 commits


05 Jul, 2012

5 commits


04 Jul, 2012

4 commits


02 Jul, 2012

5 commits


29 Jun, 2012

5 commits


28 Jun, 2012

4 commits


25 Jun, 2012

1 commit


19 Jun, 2012

1 commit


17 Jun, 2012

3 commits


16 Jun, 2012

2 commits


15 Jun, 2012

1 commit


11 Jun, 2012

1 commit


08 Jun, 2012

1 commit


05 Jun, 2012

1 commit