BigW Consortium Gitlab

  1. 20 Feb, 2016 1 commit
    • Flush emptiness caches whenever needed · e0cb3212
      Yorick Peterse authored
      This ensures that the emptiness cache (used for Repository#empty? and
      Repository#has_visible_content?) is flushed after comitting changes
      (using the web editor, API or Git) for new repositories. Once a
      repository is no longer empty there's no need to explicitly flush the
      cache for Repository#empty?. The cache for
      Repository#has_visible_content? in turn is already flushed whenever
      needed.
      
      Fixes gitlab-org/gitlab-ce#13387
  2. 19 Feb, 2016 3 commits
  3. 18 Feb, 2016 3 commits
    • Handle raw_repository returning nil in exists? · 5b6d347f
      Yorick Peterse authored
      If path_with_namespace is nil Repository#raw_repository will also return
      nil. Apparently code out there creates a Repository instance without a
      namespace path. Right.
    • Added specs for Repository#exists? · 8a7aad77
      Yorick Peterse authored
    • Only set autocrlf when creating/updating files · c475b171
      Yorick Peterse authored
      Setting the "autocrlf" Git option is an overkill since it's rarely
      actually needed. More importantly, it has quite the impact on
      performance (see gitlab-org/gitlab-ce#13457 for more information).
      
      By setting "autocrlf" when creating or updating files we guarantee the
      option is always set properly when we actually need it _without_
      introducing overhead for requests that have nothing to do with this
      option.
      
      Fixes gitlab-org/gitlab-ce#13457
  4. 17 Feb, 2016 1 commit
  5. 09 Feb, 2016 1 commit
    • Smarter flushing of branch statistics caches · 2ce0d063
      Yorick Peterse authored
      Instead of flushing the behind/ahead counts for all branches upon every
      push we now only flush the cache of branches that actually need to have
      these statistics recalculated. There are now basically 2 scenarios and
      their effects:
      
      1. A user pushes a commit to the default branch, this results in the
         cache being flushed for all branches.
      2. A user pushes to a non default branch, this results in _only_ the
         cache for that branch being flushed.
      
      The existing code (Repository#expire_cache) remains backwards compatible
      with the previous behaviour, the new behaviour is only applied when a
      branch name is passed as an argument. This ensures that when for example
      a project is deleted the cache for all branches is flushed.
  6. 08 Feb, 2016 2 commits
    • Cache various Repository Git operations · 9a99d8e4
      Yorick Peterse authored
      This caches the output of the following methods:
      
      * Repository#empty?
      * Repository#has_visible_content?
      * Repository#root_ref
      
      The cache for Repository#has_visible_content? is flushed whenever a
      commit is pushed to a new branch or an existing branch is removed.
      The cache for Repository#root_ref is only flushed whenever a user
      changes the default branch of a project. The cache for Repository#empty?
      is never explicitly flushed as there's no need for it.
  7. 21 Jan, 2016 1 commit
  8. 10 Dec, 2015 1 commit
  9. 09 Dec, 2015 1 commit
  10. 03 Dec, 2015 2 commits
  11. 02 Nov, 2015 1 commit
  12. 29 Oct, 2015 6 commits
  13. 15 Oct, 2015 1 commit
  14. 11 Aug, 2015 4 commits
  15. 16 Jul, 2015 1 commit
  16. 12 Jul, 2015 1 commit
  17. 01 Jul, 2015 2 commits
  18. 22 Mar, 2015 1 commit
  19. 18 Mar, 2015 1 commit
  20. 10 Mar, 2015 1 commit
    • This MR extends the commit calendar so it searches for commits made with every… · b26ab0ce
      Stan Hu authored
      This MR extends the commit calendar so it searches for commits made with every email address the user has associated with his account.
      
      This fixes one of the problems mentioned in gitlab-org/gitlab-ce#1162 and makes the behavior of the commit calendar as described in the profile.
      "All email addresses will be used to identify your commits."
  21. 12 Feb, 2015 1 commit
  22. 29 Sep, 2014 2 commits
  23. 31 Mar, 2013 1 commit
  24. 04 Jan, 2013 1 commit