Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-09-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-04-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-03-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-01-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-12-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-11-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-11-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-10-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-04-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-02-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-01-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-01-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-10-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-09-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-09-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-06-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-06-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-06-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2017-12-11 | Add cop for use of remove_column | Sean McGivern | |
remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration. | |||
2017-05-29 | New Migration/UpdateColumnInBatches cop | Rémy Coutable | |
Signed-off-by: Rémy Coutable <remy@rymai.me> | |||
2016-06-29 | Added RuboCop cops for checking DB migrations | Yorick Peterse | |
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. |