1. 07 3月, 2016 1 次提交
  2. 04 3月, 2016 1 次提交
  3. 24 2月, 2016 1 次提交
  4. 19 2月, 2016 1 次提交
    • R
      Add a `Blob` model that wraps `Gitlab::Git::Blob` · 8c454b36
      Robert Speicher 提交于
      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.
      8c454b36
  5. 02 2月, 2016 1 次提交
  6. 22 1月, 2016 1 次提交
  7. 20 1月, 2016 2 次提交
  8. 19 1月, 2016 1 次提交
  9. 14 1月, 2016 2 次提交
  10. 13 1月, 2016 1 次提交
  11. 30 12月, 2015 1 次提交
  12. 29 12月, 2015 1 次提交
  13. 18 12月, 2015 3 次提交
  14. 09 12月, 2015 2 次提交
  15. 07 12月, 2015 2 次提交
  16. 02 12月, 2015 1 次提交
  17. 09 9月, 2015 1 次提交
  18. 26 8月, 2015 1 次提交
  19. 29 7月, 2015 2 次提交
    • S
      Add HTMLGitlab formatter · 00ff84d3
      Stefan Tatschner 提交于
      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!
      00ff84d3
    • S
      Replace Rugments with Rouge · f736721c
      Stefan Tatschner 提交于
      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!
      f736721c
  20. 28 5月, 2015 1 次提交
  21. 20 5月, 2015 1 次提交
  22. 19 5月, 2015 1 次提交
  23. 28 3月, 2015 1 次提交
  24. 15 2月, 2015 1 次提交
    • V
      Upgrade to Rails 4.1.9 · 76aad9b7
      Vinnie Okada 提交于
      Make the following changes to deal with new behavior in Rails 4.1.2:
      
      * Use nested resources to avoid slashes in arguments to path helpers.
      76aad9b7
  25. 27 1月, 2015 1 次提交
  26. 15 1月, 2015 1 次提交
    • S
      Replace highlight.js with rouge-fork rugments · bf079c24
      Stefan Tatschner 提交于
      I decided to create a fork of rouge as rouge lacks a HTML formatter with
      the required options such as wrapping a line with <span> tags.
      Furthermore I was not really convinced about the clarity of rouge's
      source code.
      
      Rugments 1.0.0beta3 for now only includes some basic linting and a new
      HTML formatter. Everything else should behave the same.
      bf079c24
  27. 03 12月, 2014 1 次提交
  28. 18 11月, 2014 1 次提交
  29. 07 6月, 2014 1 次提交