An error occurred fetching the project authors.
- 25 Jul, 2017 3 commits
-
-
Oswaldo Ferreira authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
These don't seem to be used anywhere, so can be removed.
-
- 24 Jul, 2017 6 commits
-
-
Tim Zallmann authored
-
Jarka Kadlecova authored
-
Nick Thomas authored
-
Filipa Lacerda authored
-
Jarka Kadlecova authored
-
Ahmad Sherif authored
-
- 22 Jul, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Nick Thomas authored
-
- 21 Jul, 2017 5 commits
-
-
Nick Thomas authored
RE2 differs from Ruby in handling multiple-line strings. The string "foo\n" will not match the regular expression "foo$" unless multi-line mode is enabled (and it's off by default). Since we're already scanning the build trace line by line (and so multi-line coverage regular expressions won't work), we can fix this by removing the line separator before scanning the string.
-
Felipe Artur authored
-
Sean McGivern authored
Fix an infinite loop in Gitlab:UntrustedRegexp See merge request !2146
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
First commit in probably 2, for resolve gitlab-org/gitlab-ce#15582. This commit is renaming files and classes from build to pipeline. Also wording is editted to pipeline. Given `pipeline` had more characters than `build`, I've made the field a bit wider. The width now matchers the one for the coverage badge, so they look nice when in a table format, or in a list. As soon as this commit is merged to master, and released, the build.svg is deprecated, meaning that all users which already placed a badge should update it. However, to make sure it keeps working tests are added for this case.
-
- 20 Jul, 2017 7 commits
-
-
Alejandro Rodríguez authored
Fixes an issue where, when using branch versions, the component wouldn't be updated after the first branch checkout. We also save one step, since checking out the FETCH_HEAD with `-f` already does what `reset --hard` did.
-
Ahmad Sherif authored
Closes gitaly#396
-
Alejandro Rodríguez authored
-
Alexander Randa authored
-
Dmitriy Zaporozhets authored
New version of the gem returns 200 status code on delete with content instead of 204 so we explicitly set status code to keep existing behavior Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Lin Jen-Shin authored
-
Douwe Maan authored
24570 use re2 for user supplied regexp 9 3 See merge request !2129
-
- 19 Jul, 2017 12 commits
-
-
Lin Jen-Shin authored
-
Ahmad Sherif authored
-
Andrew Newdigate authored
-
Lin Jen-Shin authored
-
Jarka Kadlecova authored
-
Lin Jen-Shin authored
I realized where the N+1 queries were actually coming from project.protected_branches, but how come we cannot preload this, or cache this at all? Then I found that this is somehow a Rails limitation. What we're doing before, eventually come to: project.protected_branches.matching But why it's not cached? (project.protected_branches.loaded? is always false) It's because matching is a class method, which is called on the proxy. In this case, Rails cannot cache the result. I don't know if this is possible to implement or not, because clearly this would require some tricks to implement class methods on associations. So instead, we could just pass project.protected_branches to ProtectedRef.matching, then it would work regularly. With this change, there's no more N+1 queries.
-
Huang Tao authored
-
Grzegorz Bizon authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Paweł Chojnacki authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 18 Jul, 2017 5 commits
-
-
Alejandro Rodríguez authored
-
Alejandro Rodríguez authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Bob Van Landuyt authored
-
Lin Jen-Shin authored
Also make sure pipeline would also check against tag as well
-