30 Nov, 2012
1 commit
-
bugfix: backup data retrieved with the same type keys as saved
28 Nov, 2012
1 commit
-
fix resque start
25 Nov, 2012
3 commits
24 Nov, 2012
1 commit
23 Nov, 2012
1 commit
22 Nov, 2012
1 commit
-
In backup_create, backup information hash is using symbol as its key. But in backup_restore, string key is used and it returns empty value.
21 Nov, 2012
1 commit
19 Nov, 2012
1 commit
11 Nov, 2012
1 commit
-
Conflicts: doc/install/installation.md
08 Nov, 2012
1 commit
-
Also updated status task and installation instuctions.
30 Oct, 2012
1 commit
27 Oct, 2012
1 commit
09 Oct, 2012
2 commits
26 Sep, 2012
1 commit
10 Sep, 2012
1 commit
07 Sep, 2012
1 commit
-
fix bulk_import for #1309
06 Sep, 2012
2 commits
04 Sep, 2012
1 commit
-
Closes #1072
29 Aug, 2012
1 commit
-
Simplified gitolite handle logic Stubn over monkeypatch Stub only specific methods in Gitlab:Gitolite Moved grach auth to lib added specs for keys observer removes SshKey role
28 Aug, 2012
4 commits
-
Fixed some hardcoded paths based on issue #1272
-
New config option: git_hooks_path
26 Aug, 2012
1 commit
23 Aug, 2012
2 commits
21 Aug, 2012
2 commits
19 Aug, 2012
1 commit
17 Aug, 2012
1 commit
13 Aug, 2012
1 commit
03 Aug, 2012
1 commit
-
Fix UMASK checking in .gitoliterc
27 Jul, 2012
2 commits
26 Jul, 2012
2 commits
-
Potential solution for current `rake gitlab:app:backup_restore` issues.
-
…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).