An error occurred fetching the project authors.
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 12 Jun, 2016 1 commit
-
-
Stan Hu authored
Here was the problem: 1. When determining whether a given blob is viewable text, gitlab_git reads the first 1024 bytes and checks with Linguist whether it is a text or binary file. 2. If the blob is text, GitLab will attempt to display it. 3. However, if the text has binary characters after the first 1024 bytes, then GitLab will attempt to load the entire contents, but the encoding will be ASCII-8BIT since there are binary characters. 4. The Error 500 results when GitLab attempts to display a mix UTF-8 and ASCII-8BIT. To fix this, we load as much data as we are willing to display so that the detection will work properly. Requires an update to gitlab_git: gitlab-org/gitlab_git!86 Closes #13826
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 20 May, 2016 3 commits
-
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
-
Zeger-Jan van de Weg authored
-
- 07 May, 2016 1 commit
-
-
Stan Hu authored
Use a custom Loofah scrubber since sanitize 2.x transformers are inadequate to handle case-sensitive SVG attributes. sanitize parses documents as HTML instead of XML, which causes all SVG attribute names (e.g. viewBox) to be downcased. * SVG element list: https://www.w3.org/TR/SVG/eltindex.html * SVG attribute list: https://www.w3.org/TR/SVG/attindex.html Closes #14555
-
- 28 Apr, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 18 Apr, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 07 Apr, 2016 1 commit
-
-
Annabel Dunstone authored
-
- 20 Mar, 2016 1 commit
-
-
Arinde Eniola authored
-
- 07 Mar, 2016 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 03 Mar, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 24 Feb, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 19 Feb, 2016 1 commit
-
-
Robert Speicher authored
This allows us to take advantage of Rails' `to_partial_path` to render the correct partial based on the Blob type, rather than cluttering the view with conditionals. It also allows (and will allow in the future) better encapsulation for Blob-related logic which makes sense for our Rails app but might not make as much sense for the core `gitlab_git` library, such as detecting if the blob is an SVG.
-
- 01 Feb, 2016 1 commit
-
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9265
-
- 21 Jan, 2016 1 commit
-
-
Douwe Maan authored
-
- 20 Jan, 2016 2 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 19 Jan, 2016 1 commit
-
-
Douwe Maan authored
-
- 14 Jan, 2016 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 12 Jan, 2016 1 commit
-
-
Rubén Dávila authored
-
- 30 Dec, 2015 1 commit
-
-
Rubén Dávila authored
* It is more performant given now we process all the diff file instead of processing line by line. * Multiline comments are highlighted correctly.
-
- 28 Dec, 2015 1 commit
-
-
Rubén Dávila authored
-
- 18 Dec, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 08 Dec, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 07 Dec, 2015 2 commits
-
-
Marin Jankovski authored
-
Marin Jankovski authored
-
- 02 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 09 Sep, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 29 Jul, 2015 2 commits
-
-
Stefan Tatschner authored
This custom formatter for rouge is needed to generate HTML output specifically for gitlab. Since its usecase is mostly suitable for gitlab it had been rejected upstream: https://github.com/jneen/rouge/pull/268 Thanks a lot to @stanhu, @jneen and @tsigo for review!
-
Stefan Tatschner authored
I have mainly created the rugments fork for the purpose of improving gitlab's highlighting. Nowadays IMO it works way better than the old highlight.js solution. But the development is stuck on my side because of a couple of personal reasons: * I have finished my studies; last months I was writing my master thesis. So there was a huge time problem. I am sorry for that. * I had to move to Munich due to getting a (paid) job. Searching a flat here is horrible... :) * Last but not least, maintaining the same code base in two seperate projects is a mess. I have decided to switch back to rouge due to several reasons: * In the beginning I was quite motivated, but since I start working on my new job next week, the best solution IMO is switching back to upstream rouge. * Rouge is continously improving: https://github.com/jneen/rouge/blob/master/CHANGELOG.md http://rouge.jneen.net/ * There should be absolutely no regressions with this change. Most likely this pull request will almost fix some minor bugs. * One less gem in gitlab is a good thing. since Gitlab is quite a huge bundle of gems. Reducing complexity should be a major milestone. Thanks a lot to @stanhu and @jneen for the review!
-