- 06 Nov, 2017 1 commit
-
-
Francisco Javier López authored
-
- 02 Nov, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 30 Oct, 2017 4 commits
-
-
Tim Zallmann authored
-
Tim Zallmann authored
-
Tim Zallmann authored
-
Tim Zallmann authored
-
- 25 Oct, 2017 1 commit
-
-
Francisco Lopez authored
Closes #25142
-
- 18 Oct, 2017 2 commits
-
-
Sean McGivern authored
We don't want the locale to be set to Brazilian Portuguese for any subsequent specs!
-
Bob Van Landuyt authored
The locale code is turned into an asset path with an underscore instead of a dash. The language codes are transformed by `I18n.locale` into a code with a dash. But the resources for translating are always stored in a path using a `_` separating the language and the region code.
-
- 07 Oct, 2017 2 commits
-
-
Jacopo authored
Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection.
-
Bob Van Landuyt authored
The helper creates a fork of a project with all provided attributes, but skipping the creation of the repository on disk.
-
- 04 Oct, 2017 4 commits
-
-
Tim Zallmann authored
-
Tim Zallmann authored
-
Tim Zallmann authored
-
Tim Zallmann authored
Tests for these new helper methods
-
- 03 Oct, 2017 2 commits
-
-
Mike Greiling authored
-
Zeger-Jan van de Weg authored
-
- 02 Oct, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 28 Sep, 2017 1 commit
-
-
Luke "Jared" Bennett authored
-
- 25 Sep, 2017 1 commit
-
-
kushalpandya authored
-
- 22 Sep, 2017 2 commits
-
-
Phil Hughes authored
This was caused by the `@projects` value being empty when the current user does not have any personal projects.
-
Tim Zallmann authored
-
- 15 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 13 Sep, 2017 3 commits
-
-
Brandon Everett authored
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
Extends the helper method to no show the banner as soon as the project has a `.gitlab-ci.yml` file on the default branch. Fixes gitlab-org/gitlab-ce#37652
-
- 12 Sep, 2017 2 commits
-
-
micael.bergeron authored
updated the spec
-
Zeger-Jan van de Weg authored
Given the default in the development and production environment is false, the negation of enabling is used in the flag to signal you'd turn it off. It reads a bit awkward, but makes us have a migration less. Fixes gitlab-org/gitlab-ce#37653
-
- 11 Sep, 2017 1 commit
-
-
Annabel Dunstone Gray authored
This reverts merge request !14148
-
- 08 Sep, 2017 2 commits
-
-
Rubén Dávila authored
Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'" This reverts merge request !13619
-
Douwe Maan authored
[9.5] Prevent a persistent XSS in the commit author block See merge request gitlab/gitlabhq!2180
-
- 07 Sep, 2017 8 commits
-
-
Yorick Peterse authored
Whenever you push to a branch GitLab will show a button to create a merge request (should one not exist already). The underlying code to display this data was quite inefficient. For example, it involved multiple slow queries just to figure out what the most recent push event was. This commit changes the way this data is retrieved so it's much faster. This is achieved by caching the ID of the last push event on every push, which is then retrieved when loading certain pages. Database queries are only executed if necessary and the cached data is removed automatically once a merge request has been created, or 2 hours after being stored. A trade-off of this approach is that we _only_ track the last event. Previously if you were to push to branch A and B then create a merge request for branch B we'd still show the widget for branch A. As of this commit this is no longer the case, instead we will only show the widget for the branch you pushed to most recently. Once a merge request exists the widget is no longer displayed. Alternative solutions are either too complex and/or too slow, hence the decision was made to settle for this trade-off. Performance Impact ------------------ In the best case scenario (= a user didn't push anything for more than 2 hours) we perform a single Redis GET per page. Should there be cached data we will run a single (and lightweight) SQL query to get the event data from the database. If a merge request already exists we will run an additional DEL to remove the cache key. The difference in response timings can vary a bit per project. On GitLab.com the 99th percentile of time spent in User#recent_push hovers between 100 milliseconds and 1 second, while the mean hovers around 50 milliseconds. With the changes in this MR the expected time spent in User#recent_push is expected to be reduced down to just a few milliseconds. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/35990
-
Ruben Davila authored
-
Annabel Dunstone Gray authored
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
- 06 Sep, 2017 1 commit
-
-
Alejandro Rodríguez authored
-