ae2d3c4170
Mention add_column_with_default in downtime guide ## What does this MR do? This extends the "What causes downtime" guide with a mention of the `add_column_with_default` migration helper. ## Are there points in the code the reviewer needs to double check? Spelling, grammar, etc. ## Why was this MR needed? Currently the guide may lead one to believe it's not possible at all to add a column with a default value. ## Does this MR meet the acceptance criteria? - [x] ~~[CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added~~ - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - Tests - [ ] All builds are passing - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5719 |
||
|---|---|---|
| .. | ||
| README.md | ||
| architecture.md | ||
| ci_setup.md | ||
| code_review.md | ||
| db_dump.md | ||
| doc_styleguide.md | ||
| gitlab_architecture_diagram.png | ||
| gitlab_diagram_overview.odg | ||
| gotchas.md | ||
| instrumentation.md | ||
| licensing.md | ||
| migration_style_guide.md | ||
| newlines_styleguide.md | ||
| omnibus.md | ||
| performance.md | ||
| profiling.md | ||
| rake_tasks.md | ||
| scss_styleguide.md | ||
| shared_files.md | ||
| shell_commands.md | ||
| sidekiq_debugging.md | ||
| sql.md | ||
| testing.md | ||
| ui_guide.md | ||
| what_requires_downtime.md | ||
README.md
Development
Outside of docs
- CONTRIBUTING.md main contributing guide
- PROCESS.md contributing process
- GitLab Development Kit (GDK) to install a development version
Styleguides
- Documentation styleguide Use this styleguide if you are contributing to documentation.
- SQL Migration Style Guide for creating safe SQL migrations
- Testing standards and style guidelines
- UI guide for building GitLab with existing CSS styles and elements
- SQL guidelines for SQL guidelines
Process
- Code review guidelines for reviewing code and having code reviewed.
Backend howtos
- Architecture of GitLab
- CI setup for testing GitLab
- Gotchas to avoid
- How to dump production data to staging
- Instrumentation
- Performance guidelines
- Rake tasks for development
- Shell commands in the GitLab codebase
- Sidekiq debugging
- What requires downtime?
Compliance
- Licensing for ensuring license compliance