feat: pass through api error messages

[jmeridth]

Pull Request

Proposed Changes

Print api error messages so user's can solve problems

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• run make lint and fix any issues that you have introduced
• run make test and ensure you have test coverage for the lines you are introducing
• If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

• Label as either fix, documentation, enhancement, infrastructure, maintenance, or breaking

[Copilot]

Pull Request Overview

This PR enhances error handling by printing detailed API error messages for various GitHub API exceptions, helping users diagnose and resolve issues.

• Capture exception objects as e and delegate to a new print_error_messages helper.
• Introduce print_error_messages to iterate through an exception’s errors list and print each message.
• Update all existing exception handlers in search_issues to call print_error_messages before exiting.

Comments suppressed due to low confidence (3)

search.py:92

• The error message is missing a closing apostrophe after the repository string. It should be names: '{repos_and_owners_string}' to balance the quote.

f"The repository could not be found; \

search.py:123

• [nitpick] Loop variable error shadows the function parameter. Rename the loop variable to something like err_item to avoid confusion.

for error in error.errors:

search.py:115

• The new helper function print_error_messages and its usage in handlers lack dedicated unit tests. Consider adding tests to verify that various errors payloads are printed correctly.

def print_error_messages(error: github3.exceptions):

[zkoppert]

Really helpful addition!