| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42 | GitLab Bot | 2021-02-18 | 1 | -0/+2 |
| | | |||||
| * | Use gitlab-styles | Rémy Coutable | 2017-12-22 | 1 | -1/+1 |
| | | | | | Signed-off-by: Rémy Coutable <remy@rymai.me> | ||||
| * | Enable Style/MutableConstant | Douwe Maan | 2017-02-23 | 1 | -1/+1 |
| | | |||||
| * | Explicitly require rubocop migration_helpersdm-add-column-with-default-cop | Douwe Maan | 2017-02-08 | 1 | -0/+2 |
| | | |||||
| * | Add cop that checks if add_column_with_default is used with up/down methods | Douwe Maan | 2017-02-08 | 1 | -1/+1 |
| | | |||||
| * | Added RuboCop cops for checking DB migrationsmigration-cops | Yorick Peterse | 2016-06-29 | 1 | -0/+46 |
| There are currently two cops for this: * Migration/AddIndex: checks if indexes are added concurrently * Migration/ColumnWithDefault: checks if columns with default values are added in a concurrent manner Both cops are fairly simple and make no attempt at correcting the code as this is quite hard to do (e.g. modifications may need to be applied in various places in the same file). They however should provide enough to catch people ignoring the comments in generated migrations telling them to use add_concurrent_index or add_column_with_default. | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |