delta/gitlab/gitlab-ce.git/rubocop/cop, branch commit-description-border gitlab.com: gitlab-org/gitlab-ce.git cop for gem fetched from a git source 2017-01-31T02:24:15+00:00 Adam Pahlevi adam.pahlevi@gmail.com 2017-01-28T04:33:38+00:00 78a3bba62e41831a1b4d994d040a0f8327a3e173 code fix for aesthetic & conventions remove unused proc 
code fix for aesthetic & conventions

remove unused proc
Added RuboCop cops for checking DB migrations 2016-06-29T12:14:02+00:00 Yorick Peterse yorickpeterse@gmail.com 2016-06-24T15:26:28+00:00 c740445ad3825da4e5f7fea943be561ece982443 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. 
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.