Skip to content

DrDroid AI: Fix: Log GitHub 403 errors as info instead of error#133

Open
doctor-droid-app[bot] wants to merge 1 commit intomasterfrom
fix-automated-debugging-i79hjhc1
Open

DrDroid AI: Fix: Log GitHub 403 errors as info instead of error#133
doctor-droid-app[bot] wants to merge 1 commit intomasterfrom
fix-automated-debugging-i79hjhc1

Conversation

@doctor-droid-app
Copy link

Summary

GitHub API 403 responses (token lacks permission to access private repos) are now logged as info instead of error, preventing unnecessary Sentry noise.

Changes

  • Updated get_pr_files to use logger.info for 403 responses
  • Updated get_pr_comments (both issue and review comment fetches) to use logger.info for 403 responses
  • Updated list_recent_commits, get_commit_files, get_commit_comments, list_pull_requests, get_pull_request, list_releases, get_release, and get_repository_info to use logger.info for 403 responses
  • All other non-200 status codes continue to use logger.error as before

Testing

  • Verified the conditional logic checks for status code 403 specifically and routes to logger.info, while all other error status codes continue to use logger.error

This PR is created as part of investigation https://aiops.drdroid.io/?investigation_id=8e590cf3-af9d-4e6c-8dc8-0e99202e1a86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants