a54af831ba
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".
|
||
|---|---|---|
| .. | ||
| architecture.md | ||
| ci_setup.md | ||
| code_review.md | ||
| db_dump.md | ||
| doc_styleguide.md | ||
| gitlab_diagram_overview.odg | ||
| gitlab_diagram_overview.png | ||
| gotchas.md | ||
| instrumentation.md | ||
| migration_style_guide.md | ||
| omnibus.md | ||
| profiling.md | ||
| rake_tasks.md | ||
| README.md | ||
| scss_styleguide.md | ||
| shared_files.md | ||
| shell_commands.md | ||
| sidekiq_debugging.md | ||
| sql.md | ||
| testing.md | ||
| ui_guide.md | ||
Development
- Architecture of GitLab
- CI setup for testing GitLab
- Code review guidelines for reviewing code and having code reviewed.
- Gotchas to avoid
- How to dump production data to staging
- Instrumentation
- Migration Style Guide for creating safe migrations
- Rake tasks for development
- Shell commands in the GitLab codebase
- Sidekiq debugging
- SQL guidelines for SQL guidelines
- Testing standards and style guidelines
- UI guide for building GitLab with existing css styles and elements