Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Repository

Switch branch/tag
  • heptapod
  • db
  • post_migrate
  • 20180305100050_remove_permanent_from_...
Find file BlameHistoryPermalink
  • Jan Provaznik's avatar
    Add version 4.2 to all existing migrations · 250df09df8a9
    Jan Provaznik authored Nov 13, 2018
    DB schema generated by a migration may look different in
    rails 4 and 5 (because rails 5 may use different default values).
    For this reason it's important to explicitly set for which rails
    version a migration was written for.
    
    See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
    250df09df8a9

Replace 20180305100050_remove_permanent_from_redirect_routes.rb

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.