<!--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=521811) </details> <!--IssueSummary end--> This issue is part of the https://gitlab.com/groups/gitlab-org/-/epics/16949 epic. See that epic's description for more context. ### About We want to remove the `octokit` gem which is used by the GitHub importer and Gitea Importer. The work includes: - Remove the `octokit` gem, [middleware](https://gitlab.com/gitlab-org/gitlab/-/blob/5a9474ddfcd29ae71df06bb36f7ed3c995252da0/config/initializers/octokit.rb#L3-4) and [patches](https://gitlab.com/gitlab-org/gitlab/-/blob/697d9564adbd77dead01390d0d30bf148150e51b/config/initializers/sawyer_patch.rb#L5). - Remove `faraday-multipart` which [was added for octokit](https://gitlab.com/gitlab-org/gitlab/-/blob/569cfc282f716eae5e1e55c791c1ccb9023175c4/Gemfile#L609-610) - being verified in https://gitlab.com/gitlab-org/gitlab/-/issues/521811#note_2371922440. - Write a small HTTP client to interact with the GitHub API. All HTTP calls must use `Gitlab::HTTP`. With special [handling of rate limits](https://gitlab.com/gitlab-org/gitlab/-/blob/8d7d4e913ab242342ae583c3459029c485145bc7/lib/gitlab/github_import/client.rb#L188). Refactor `Gitlab::GithubImport::Client`. The API interactions must be neat and maintainable. Refactoring any error handling of Octokit errors. Support Pagination and GitHub Enterprise. - Similary, refactor `Gitlab::LegacyGithubImport::Client` used by Gitea #### AppSec review On every MR, the Application Security Engineer stable counterpart for Import and Integrate ([see this page](https://handbook.gitlab.com/handbook/product/categories/#import-and-integrate-group) - `@ameyadarshan` at time of writing) must be asked to review. The review is not blocking, so can be conducted after the MR merges.