- 08 3月, 2016 3 次提交
-
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
- 02 3月, 2016 2 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 25 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This is only needed when calling the "expire_cache" method as the other expiration methods don't depend on Git data.
-
- 23 2月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
-
由 Yorick Peterse 提交于
This keeps all the cache expiration code in a single file/class instead of spreading it all across the codebase.
-
- 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 22 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
* Now checking if a commit is already reverted or there is a conflict is much more faster. * No longer need to create a new branch.
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
* Not required to run hooks since it's an internal commit
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 18 2月, 2016 4 次提交
-
-
由 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 提交于
Just checking raw_repository is no longer accurate to determine if a repository exists or not.
-
由 Yorick Peterse 提交于
Now that Repository#raw_repository no longer sets the autocrlf option it will also no longer raise any NoRepository errors since it doesn't access Rugged any more. This also means that Repository#exists? can't simply return the raw repository as this is no indication of whether or not the repository actually exists (besides returning a non boolean is weird in the first place). To solve this problem Repository#exists? now properly checks if the repository exists and returns true/false instead of a Gitlab::Git::Repository or nil object.
-
由 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 3 次提交
-
-
由 Mark Riedesel 提交于
-
由 Yorick Peterse 提交于
This ensures that _all_ caches (including any caches normally only flushed under certain conditions) are flushed whenever a project is removed. Because cache keys are based on project namespaces (excluding IDs) not doing so could result in a newly created project re-using old caches (if the project was re-created using the same name).
-
由 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
-
- 16 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
The "default_branch" argument is never used and the "project" argument isn't optional.
-
- 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.
-