An error occurred fetching the project authors.
- 23 Oct, 2015 3 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>
-
Kamil Trzcinski authored
-
- 22 Oct, 2015 7 commits
-
-
Stan Hu authored
Cloning a project Wiki over HTTP would end up cloning the main repository since the .wiki extension was being stripped. Closes #3106
-
Valery Sizov authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Robert Speicher authored
[ci skip]
-
Kamil Trzcinski authored
-
Douwe Maan authored
-
- 21 Oct, 2015 6 commits
-
-
Stan Hu authored
Closes #3094
-
Artem V. Navrotskiy authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9753
-
Job van der Voort authored
The logo is now rendered as pure SVG, rather than image referencing a svg. The SVG has an id and the shapes of the logo have a shared class. The shapes change their fill color on hover with a transition.
-
- 20 Oct, 2015 5 commits
-
-
Jacob Vosmaer authored
-
Stan Hu authored
Safari 9.0 does not yet honor the HTML5 `origin-when-cross-origin` mode, and it's possible load balancers/proxies strip the HTTP_REFERER from the request header. In these cases, default to some default path. Closes #3122 Closes https://github.com/gitlabhq/gitlabhq/issues/9731
-
Yorick Peterse authored
If a node is ignored there's no need for searching for a given pattern. In turn, when searching for the pattern there's no need to construct a MatchData object as we only care about presence (or lack thereof), not the resulting matches. In terms of performance this cuts down about 200 ms when loading issue #2164 locally, though this varies a bit depending on system load.
-
Maurice Mohlek authored
-
Maurice Mohlek authored
-
- 19 Oct, 2015 4 commits
-
-
Stan Hu authored
By default, all the current user's repositories are accessible via the /users endpoint. There's no need to traverse all the organization repositories as well. See: * http://www.rubydoc.info/github/pengwynn/octokit/Octokit/Client/Repositories#repositories-instance_method * https://developer.github.com/v3/repos/#list-your-repositories Closes #2523
-
Douwe Maan authored
-
Yorick Peterse authored
This cuts down the time it takes to sort issues of a milestone by about 10x. In the previous setup the code would run a SQL query for every issue that had to be sorted. The new setup instead runs a single SQL query to update all the given issues at once. The attached benchmark used to run at around 60 iterations per second, using the new setup this hovers around 600 iterations per second. Timing wise a request to update a milestone with 40-something issues would take about 760 ms, in the new setup this only takes about 130 ms. Fixes #3066
-
Douwe Maan authored
[ci skip]
-
- 18 Oct, 2015 5 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 17 Oct, 2015 1 commit
-
-
Stan Hu authored
The counter_cache decrement function is called when a project star is deleted, but there was no guarantee multiple workers would not attempt to delete the same item simultaneously. Use an atomic update to prevent the count from going negative. Closes #3067
-
- 16 Oct, 2015 6 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Zeger-Jan van de Weg authored
Credits to Douwe Maan
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Zeger-Jan van de Weg authored
-
Douwe Maan authored
-
Stan Hu authored
If a branch is deleted with an open merge request, amended offline, and then pushed again, GitLab doesn't bother to update the merge request even though the last commit ID and/or code may have changed. This MR ensures that each push will update any relevant merge requests and adds a system note if this happens as well. Closes #2926
-
- 15 Oct, 2015 3 commits
-
-
Kamil Trzcinski authored
-
Yorick Peterse authored
-
Yorick Peterse authored
Performance is improved in two steps: 1. On PostgreSQL an expression index is used for checking lower(email) and lower(username). 2. The check to determine if we're searching for a username or Email is moved to Ruby. Thanks to @haynes for suggesting and writing the initial implementation of this. Moving the check to Ruby makes this method an additional 1.5 times faster compared to doing the check in the SQL query. With performance being improved I've now also tweaked the amount of iterations required by the User.by_login benchmark. This method now runs between 900 and 1000 iterations per second.
-