Gh test3

[BrandonwLii]

No description provided.

[github-actions]

Key Features

• Introduction of new data models using Pydantic for better structure and validation.
• Enhanced search functionality with the addition of CodeRagAgent and SummaryAgent.
• Improved handling of search queries and results, including relevance checking.
• Refactoring of the PRReviewAgent to streamline the process of generating summaries and posting to GitHub.

Summary of Changes

This pull request introduces significant changes to the PR_agent.py, code_rag_agent.py, and summary_agent.py files. Key modifications include the addition of new classes for handling search results and relevance checks, as well as refactoring existing methods to improve clarity and functionality. The PRReviewAgent now utilizes new agents for generating search queries and summaries, enhancing its ability to process pull requests effectively.

New Unlocks from Functionality

• The ability to generate structured search queries based on code changes in a pull request.
• Improved relevance checking for search results, allowing for more accurate filtering of relevant code snippets.
• A more organized approach to generating summaries of pull requests, which can be posted directly to GitHub.

Code Suggestions with Line Number References

1. Line 8-9: In the PRReviewContext class, the desciption key is misspelled. It should be corrected to description for consistency and to avoid potential issues.
2. Line 54: The self.queryAgent initialization could benefit from a docstring explaining its purpose and how it interacts with the rest of the class.
3. Line 115: The post_to_github method should include error handling for the GitHub API call to ensure that failures are logged or managed appropriately.

Formatting Suggestions

• Ensure consistent spacing and indentation throughout the code. For example, there are inconsistent spaces around the = operator in several places (e.g., default = True should be default=True).
• Consider adding more comments to complex sections of the code to improve readability and maintainability, especially in the next_turn method where multiple operations are performed.

Additional Notes

• The introduction of print statements for debugging (e.g., print("queries: "+str(queries))) should be replaced with proper logging before merging to avoid cluttering the output in production.
• It would be beneficial to add unit tests for the new functionality, particularly for the Searches and RelevanceResult classes, to ensure they behave as expected.
• Consider potential edge cases where the search results may return empty or malformed data, and ensure that the code handles these scenarios gracefully.