An error occurred fetching the project authors.
- 21 Oct, 2017 1 commit
-
- 19 Oct, 2017 1 commit
-
- 07 Oct, 2017 1 commit
-
-
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.
-
- 02 Oct, 2017 1 commit
-
-
Jose Ivan Vargas authored
-
- 15 Aug, 2017 1 commit
-
-
Phil Hughes authored
The dispatcher was trying to create a new instance of a class that is loaded in a file after main.js which would cause the filtered search to not work on issues. This would only happen on the first load when the JS is not cached. If the JS is cached, then everything will be fine.
-
- 27 Jul, 2017 2 commits
-
-
Robert Speicher authored
-
Keifer Furzland authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 13 Jul, 2017 1 commit
-
-
Bob Van Landuyt authored
Otherwise some features would go untested in non-specific contexts I did need to disable the `gitlab_git_diff_size_limit_increase`-feature in some specs since we depend on diffs being expandable while the file we are testing on is smaller than the increased limit.
-
- 06 Jul, 2017 1 commit
-
-
Robert Speicher authored
-
- 05 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 29 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 19 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 17 Jun, 2017 1 commit
-
-
Stan Hu authored
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 02 Jun, 2017 1 commit
-
-
Sean McGivern authored
This is controlled with the feature flag gitlab_git_diff_size_limit_increase. Both of these limits were basically picked arbitrarily in the first place; disabling the feature flag reverts to the old limits.
-
- 22 May, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 10 May, 2017 1 commit
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 21 Apr, 2017 1 commit
-
-
Jacopo authored
Removed all the unnecessary include of `WaitForAjax` and `ApiHelpers` in the specs. Removed unnecessary usage of `api:true`
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 10 Feb, 2017 1 commit
-
-
Annabel Dunstone Gray authored
-
- 02 Dec, 2016 1 commit
-
-
Annabel Dunstone Gray authored
-
- 13 Oct, 2016 7 commits
-
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
- Use a store base object to manage application state. - Add a service to handle ajax requests. - Load code only when needed
-
Sean McGivern authored
-
Alfredo Sumaran authored
-
Douwe Maan authored
-
- 25 Aug, 2016 1 commit
-
-
Sean McGivern authored
These can't be resolved in the UI because if they aren't in a UTF-8 compatible encoding, they can't be rendered as JSON. Even if they could, we would be implicitly changing the file encoding anyway, which seems like a bad idea.
-
- 17 Aug, 2016 1 commit
-
-
Sean McGivern authored
These JS errors are only thrown in PhantomJS, and enough of the page is rendered properly that this spec passes. We should remove this in future.
-
- 12 Aug, 2016 2 commits
-
-
Fatih Acet authored
-
Sean McGivern authored
-