- 20 Feb, 2016 1 commit
-
-
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
-
- 19 Feb, 2016 3 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 18 Feb, 2016 3 commits
-
-
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.
-
Yorick Peterse authored
-
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
-
- 17 Feb, 2016 1 commit
-
-
Yorick Peterse authored
This ensures the caches for Repository#empty? and Repository#has_visible_content? are flushed after a repository has been imported or forked. Fixes gitlab-org/gitlab-ce#13505
-
- 09 Feb, 2016 1 commit
-
-
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.
-
- 08 Feb, 2016 2 commits
-
-
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.
-
Tony Chu authored
-
- 21 Jan, 2016 1 commit
-
-
Yorick Peterse authored
Gitlab::Git::Repository#branch_count is a tad faster than the previous setup. See gitlab-org/gitlab_git!62 for more information.
-
- 10 Dec, 2015 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 09 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Dec, 2015 2 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 02 Nov, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 29 Oct, 2015 6 commits
-
-
Michael Chmielewski authored
-
Michael Chmielewski authored
Fixed method to use git log via Popen as recommended, and made output match test (and thus system) expectations.
-
Michael Chmielewski authored
-
Michael Chmielewski authored
-
Mike Chmielewski authored
-
Jonathan Schoeffling authored
Include the log messages of recent commits in project-level search results, providing functionality similar to 'git log --grep'. Update repository model rspec tests to validate the output of Repository#commits_with_log_matching.
-
- 15 Oct, 2015 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 11 Aug, 2015 4 commits
-
-
Florent (HP) authored
-
Dmitriy Zaporozhets authored
This reverts commit 5daf44b7, reversing changes made to 2f706fbd.
-
Dmitriy Zaporozhets authored
This reverts commit 459e6d34, reversing changes made to 804168e1. Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
This reverts commit 957e849f, reversing changes made to 6b9dbe9f. Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 16 Jul, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 Jul, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 01 Jul, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 22 Mar, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Mar, 2015 1 commit
-
-
Hannes Rosenögger authored
-
- 10 Mar, 2015 1 commit
-
-
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."
-
- 12 Feb, 2015 1 commit
-
-
Jeroen van Baarsen authored
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 29 Sep, 2014 2 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 31 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 04 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-