refactor(github): use Octokit REST namespace - #3166
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe GitHub client now uses Octokit’s ChangesOctokit REST migration
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/hold |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petersutter The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. DetailsGit tree hash: ef4356682be3ea1fb24aba2dacd2e9fa6d9afca1 |
fwiw I tested it and it seems to still work |
How to categorize this PR?
/area dev-productivity
/kind cleanup
What this PR does / why we need it:
Migrates the GitHub integration from Octokit's legacy root-level REST methods to the
octokit.restnamespace. This removes reliance on the compatibility API while preserving the existing issue search, update, and comment behavior.Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
This follows the Octokit major update from #3146. The full pre-push verification completed successfully.
Release note:
Summary by CodeRabbit