381468d0cc
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.
16 lines
485 B
Ruby
16 lines
485 B
Ruby
# 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
|