gitlab-org--gitlab-foss/db/migrate/20190621151636_add_merge_re...

# frozen_string_literal: true

class AddMergeRequestRebaseJid < ActiveRecord::Migration[5.1]
  DOWNTIME = false

  def change
    add_column :merge_requests, :rebase_jid, :string # rubocop:disable Migration/PreventStrings
  end
end
Allow asynchronous rebase operations to be monitored This MR introduces tracking of the `rebase_jid` for merge requests. As with `merge_ongoing?`, `rebase_in_progress?` will now return true if a rebase is proceeding in sidekiq. After one release, we should remove the Gitaly-based lookup of rebases. It is much better to track this kind of thing via the database. 2019-06-21 16:56:47 +00:00			`# frozen_string_literal: true`

			`class AddMergeRequestRebaseJid < ActiveRecord::Migration[5.1]`
			`DOWNTIME = false`

			`def change`
Add latest changes from gitlab-org/gitlab@master 2020-04-21 15:21:10 +00:00			`add_column :merge_requests, :rebase_jid, :string # rubocop:disable Migration/PreventStrings`
Allow asynchronous rebase operations to be monitored This MR introduces tracking of the `rebase_jid` for merge requests. As with `merge_ongoing?`, `rebase_in_progress?` will now return true if a rebase is proceeding in sidekiq. After one release, we should remove the Gitaly-based lookup of rebases. It is much better to track this kind of thing via the database. 2019-06-21 16:56:47 +00:00			`end`
			`end`