- 20 2月, 2016 25 次提交
-
-
由 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 提交于
-
由 Rubén Dávila 提交于
* Not required to run hooks since it's an internal commit
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
+ minor improvements
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 19 2月, 2016 3 次提交
-
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
- add feature to list runners - add feature to show runners details - add feature to delete runner - add feature to update runner
-
由 Robert Speicher 提交于
-
- 18 2月, 2016 5 次提交
-
-
由 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
-
由 Rubén Dávila 提交于
-
- 17 2月, 2016 5 次提交
-
-
由 Rémy Coutable 提交于
Fixes #13367.
-
-
由 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 2 次提交
-
-
由 Rémy Coutable 提交于
-
由 Rémy Coutable 提交于
-