Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

rubocop

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Yorick Peterse authored
    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.
    c740445a
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.