<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=440843) </details> <!--IssueSummary end--> !142980 moved `Gitlab::GithubImport::RefreshImportJidWorker` to a more generic namespace now that it's used by Bitbucket importers: `Gitlab::Import::RefreshImportJidWorker`. However, the old worker was left in place and simply enqueued the renamed worker, effectively making it a no-op per our [documentation on removing workers](https://docs.gitlab.com/ee/development/sidekiq/compatibility_across_updates.html#removing-worker-classes). Once the initial MR is merged to production and `Gitlab::Import::RefreshImportJidWorker` is successfully being enqueued, `Gitlab::GithubImport::RefreshImportJidWorker` and its specs can safely be removed.