gitlab-org--gitlab-foss/app/workers/rebase_worker.rb

# frozen_string_literal: true

# The RebaseWorker must be wrapped in important concurrency code, so should only
# be scheduled via MergeRequest#rebase_async
class RebaseWorker
  include ApplicationWorker

  def perform(merge_request_id, current_user_id)
    current_user = User.find(current_user_id)
    merge_request = MergeRequest.find(merge_request_id)

    MergeRequests::RebaseService
      .new(merge_request.source_project, current_user)
      .execute(merge_request)
  end
end
Enable frozen string literals for app/workers/*.rb 2018-06-27 07:23:28 +00:00			`# frozen_string_literal: true`

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			`# The RebaseWorker must be wrapped in important concurrency code, so should only`
			`# be scheduled via MergeRequest#rebase_async`
Backport 'Rebase' feature from EE to CE When a project uses fast-forward merging strategy user has to rebase MRs to target branch before it can be merged. Now user can do rebase in UI by clicking 'Rebase' button instead of doing rebase locally. This feature was already present in EE, this is only backport of the feature to CE. Couple of changes: * removed rebase license check * renamed migration (changed timestamp) Closes #40301 2017-12-20 09:01:21 +00:00			`class RebaseWorker`
			`include ApplicationWorker`

			`def perform(merge_request_id, current_user_id)`
			`current_user = User.find(current_user_id)`
			`merge_request = MergeRequest.find(merge_request_id)`

			`MergeRequests::RebaseService`
			`.new(merge_request.source_project, current_user)`
			`.execute(merge_request)`
			`end`
			`end`