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).
18 Jul, 2012
1 commit
10 Jul, 2012
2 commits
02 Jul, 2012
2 commits
25 Jun, 2012
1 commit
17 Jun, 2012
2 commits
16 Jun, 2012
2 commits
15 Jun, 2012
1 commit
-
* Profile * Browse code * Sceleton for main features * Wiki * Commits
26 May, 2012
1 commit
22 Apr, 2012
2 commits
21 Apr, 2012
2 commits
-
Conflicts: app/assets/javascripts/merge_requests.js db/schema.rb
04 Apr, 2012
1 commit
30 Mar, 2012
1 commit
-
… gitlab user be able to push to any repo
11 Mar, 2012
1 commit
09 Mar, 2012
1 commit
06 Mar, 2012
1 commit
29 Feb, 2012
1 commit
27 Dec, 2011
1 commit
-
Conflicts: app/models/project.rb config/routes.rb db/schema.rb
16 Dec, 2011
2 commits
-
Bulk repo import Rake task
15 Dec, 2011
2 commits
13 Dec, 2011
3 commits
-
Git repos should be in the import_projects directory in the root of application. The task is invoked via @rake import_projects@.
-
- Better comment too
12 Dec, 2011
1 commit
05 Dec, 2011
2 commits
15 Nov, 2011
1 commit
09 Oct, 2011
1 commit