- 03 Jun, 2016 1 commit
-
-
Connor Shea authored
Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize. The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance. The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product. An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded. Rainbow library: https://github.com/sickill/rainbow Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
-
- 03 Nov, 2015 1 commit
-
-
Robert Speicher authored
Closes #3311
-
- 23 Jun, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Jun, 2015 1 commit
-
-
Marin Jankovski authored
-
- 20 Mar, 2015 1 commit
-
-
Andrew Tomaka authored
-
- 12 Dec, 2014 2 commits
-
-
Marin Jankovski authored
-
Marin Jankovski authored
-
- 11 Dec, 2014 1 commit
-
-
Marin Jankovski authored
-
- 18 Nov, 2014 2 commits
-
-
Dmitriy Zaporozhets authored
This reverts commit 533f4cdf.
-
Ciro Santilli authored
Before this it would fail because git hooks automatically prepend things to the path, which can lead the wrong Ruby version to be called in which dependencies are not installed. To make sure that this is correct, the forked_merge_requests commented out test that depends on this change was uncommented. For that test to pass, it is also necessary to setup the mock server on port 3001 under test_env.rb.
-
- 05 Nov, 2014 2 commits
-
-
Ciro Santilli authored
-
Ciro Santilli authored
-
- 18 Oct, 2014 2 commits
-
-
Ciro Santilli authored
Faster, more portable and less error prone since no shell expansion.
-
Ciro Santilli authored
-
- 15 Oct, 2014 1 commit
-
-
Ciro Santilli authored
-
- 22 Sep, 2014 2 commits
-
-
Ciro Santilli authored
-
Jacob Vosmaer authored
-
- 26 Aug, 2014 1 commit
-
-
Jacob Vosmaer authored
This should reduce the number of gitlab-shell error messages while the tests run.
-
- 31 Jul, 2014 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 02 May, 2014 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 08 Apr, 2014 1 commit
-
-
Cyril Rohr authored
-
- 14 Mar, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 18 Jul, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Use gitlab-shell authorized_keys truncation. Fix issue with authorized_keys stored in different location
-
- 30 May, 2013 1 commit
-
-
Angus MacArthur authored
These fixes will allow a restore of gitlab when the backups and repositories directories are in non-standard locations (ie sub-dirs of gitlabhq). Also allows the restore to be run from script overriding the need of a user to confirm the rebuild of the authorized_keys file.
-
- 14 Feb, 2013 1 commit
-
-
Bhagavan Das authored
Remove hardcoded refernce to gitlab-shell home. so that gitlab can be installed on any unix account other than git
-
- 11 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 09 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 07 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-