- Jul 31, 2018
-
-
Michael Kozono authored
-
- Jul 19, 2018
-
-
Zeger-Jan van de Weg authored
Introduced by f20eadcb, meant to remove refs from Git using the wrong name. That never made it to a non-rc release and can be safely removed now.
-
- Jun 05, 2018
-
-
- Mar 21, 2018
-
-
Jacob Vosmaer (GitLab) authored
-
- Feb 28, 2018
-
-
Horatiu Eugen Vlad authored
-
- Jan 26, 2018
-
-
Lin Jen-Shin authored
-
- Jan 25, 2018
-
-
Jacob Vosmaer (GitLab) authored
-
- Jan 11, 2018
-
-
- Nov 25, 2017
-
-
digitalMoksha authored
-
digitalMoksha authored
-
- Nov 24, 2017
-
-
digitalMoksha authored
-
- Nov 21, 2017
-
-
Brett Walker authored
-
- Nov 16, 2017
-
-
Jacopo authored
Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses.
-
- Aug 30, 2017
-
-
Lin Jen-Shin authored
-
- Mar 03, 2017
-
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- Feb 23, 2017
-
-
Douwe Maan authored
-
- Feb 03, 2017
-
-
Adam Pahlevi authored
add complete changelog for !8949
-
- Nov 18, 2016
-
-
Z.J. van de Weg authored
In the 8.13 RC cycle, so before the release, there was a time in which references in git where stored by id instead of iid. This could be fixed by time, if the iid catches up with the id, it overwrites it. But in the mean time we have wrong refs in the folder. This commit fixes that. For all projects we have deployments we'll find the ones where the ref has a higher number than the iid is now and calls `#create_ref` on the corresponding deployment.
-
- Jun 30, 2016
-
-
Alejandro Rodríguez authored
-
- Jun 03, 2016
-
-
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
-
- Sep 15, 2015
-
-
Jacob Vosmaer (GitLab) authored
-
Jacob Vosmaer (GitLab) authored
Clean up more than just global (legacy) repos. Also, instead of deleting, just rename.
-
- Jun 23, 2015
-
-
Dmitriy Zaporozhets authored
-
- Jun 09, 2015
-
-
zenati authored
-
- Feb 16, 2015
-
-
Daniel Steinborn authored
-
- Nov 12, 2014
-
-
Marvin Frick authored
In e23a26ae (and later 1bc99369) the API for Gitlab::LDAP::Adapter was changed. I assume this rake task was an oversight in the refactoring of the changed class. While being on it, I noticed that already blocked users cannot be blocked again.
-
- Jun 26, 2014
-
-
Marvin Frick authored
-
- Jul 29, 2013
-
-
Johannes Schleifenbaum authored
-
- May 05, 2013
-
-
Andrey Kumanyaev authored
-
- Feb 11, 2013
-
-
Dmitriy Zaporozhets authored
-
- Feb 09, 2013
-
-
Dmitriy Zaporozhets authored
-
- Dec 25, 2012
-
-
Dmitriy Zaporozhets authored
-