- 17 3月, 2016 1 次提交
-
-
由 Hiroyuki Sato 提交于
-
- 09 3月, 2016 5 次提交
-
-
由 Yorick Peterse 提交于
This ensures the right caches are flushed when adding a branch via the UI, instead of only flushing this one random cache.
-
由 Yorick Peterse 提交于
This ensures Repository#add_tag calls Repository#before_push_tag instead of just 1 random cache expiration method.
-
由 Yorick Peterse 提交于
-
由 Yorick Peterse 提交于
This ensures that Repository#rm_branch calls before_remove_branch/after_remove_branch instead of just 1 random cache expiration method.
-
由 Yorick Peterse 提交于
The methods used for this are Repository#tag_count and Repository#branch_count which cache their output in Redis as well as memoizing it in an instance variable. Both methods have a corresponding methods/hooks to flush the caches at the right time.
-
- 08 3月, 2016 2 次提交
-
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
- 02 3月, 2016 1 次提交
-
-
由 Rubén Dávila 提交于
-
- 25 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
-
- 21 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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
-
- 20 2月, 2016 3 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 18 2月, 2016 3 次提交
-
-
由 Yorick Peterse 提交于
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 提交于
-
由 Yorick Peterse 提交于
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 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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
-
- 10 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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 2月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
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 提交于
-
- 22 1月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
Gitlab::Git::Repository#branch_count is a tad faster than the previous setup. See gitlab-org/gitlab_git!62 for more information.
-
- 10 12月, 2015 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 09 12月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 03 12月, 2015 2 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 02 11月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 29 10月, 2015 6 次提交
-
-
由 Michael Chmielewski 提交于
-
由 Michael Chmielewski 提交于
Fixed method to use git log via Popen as recommended, and made output match test (and thus system) expectations.
-
由 Michael Chmielewski 提交于
-
由 Michael Chmielewski 提交于
-
由 Mike Chmielewski 提交于
-
由 Jonathan Schoeffling 提交于
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.
-
- 16 10月, 2015 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 12 8月, 2015 1 次提交
-
-
由 Florent (HP) 提交于
-
- 11 8月, 2015 3 次提交
-
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 5daf44b7, reversing changes made to 2f706fbd.
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 459e6d34, reversing changes made to 804168e1. Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
This reverts commit 957e849f, reversing changes made to 6b9dbe9f. Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 16 7月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 7月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-