Yorick Peterse a54af831ba Use rake db:reset instead of db:setup ... Using db:reset ensures existing tables are first dropped. This in turn ensures that we can drop tables regardless of any foreign key constraints. While CE currently doesn't have any foreign keys EE defines the following relation: remote_mirrors.project_id -> projects.id MySQL will complain whenever you try to drop the "projects" table first even when using "DROP TABLE ... CASCADE".		2016-04-14 15:53:54 +02:00
..
ci	Migrate CI::Project to Project	2015-12-11 18:02:09 +01:00
gitlab	Use rake db:reset instead of db:setup	2016-04-14 15:53:54 +02:00
migrate
.gitkeep
brakeman.rake	Reduce progress bar noise during brakeman run	2016-03-04 22:12:25 +00:00
cache.rake	Put CACHE_NAMESPACE in the Gitlab::Redis module	2016-04-07 15:42:07 +02:00
dev.rake
flay.rake	Set higher flay value to avoid unnecessary refactoring for now	2015-11-17 11:18:01 +01:00
flog.rake
gemojione.rake	fix emoji aliases not showing in autocomplete	2016-04-09 13:29:37 +01:00
grape.rake	Add grape routing print	2015-11-12 16:26:23 +01:00
rubocop.rake
scss-lint.rake	Add SCSS Lint, CSSComb config file, run SCSS Lint in GitLab CI, add documentation for SCSS Style Guide.	2016-03-14 20:33:54 -06:00
services.rake
setup.rake
sidekiq.rake
spec.rake	Removed benchmark suite and its documentation	2016-03-10 11:15:43 +01:00
spinach.rake	Retry spinach tests	2016-03-09 14:22:32 +01:00
test.rake