Add logging for skipping non-code files in GitHub provider

[mrT23]

PR Type

enhancement, logging

---

Description

• Added logging to inform when non-code files are skipped in the GitHub provider.

---

Changes walkthrough 📝

	Relevant files
Enhancement	github_provider.py Add logging for non-code file skips in GitHub provider      pr_agent/git_providers/github_provider.py Added logging for skipping non-code files in the GitHub provider. +1/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the PR is small and involves a straightforward addition of a logging statement. The change is localized to a single function and does not involve complex logic or modifications to existing functionality.
🏅 Score	95
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Performance	Store the logger instance in a variable outside the loop to avoid repeated calls to get_logger() To avoid potential performance issues and ensure the logger is only created once, store the logger instance in a variable outside the loop. pr_agent/git_providers/github_provider.py [148-150] +logger = get_logger() for file in files: if not is_valid_file(file.filename): - get_logger().info(f"Skipping a non-code file: {file.filename}") + logger.info(f"Skipping a non-code file: {file.filename}") continue Suggestion importance[1-10]: 7 Why: Creating the logger instance outside the loop can indeed improve performance by reducing redundant object creation. This suggestion is relevant and improves the efficiency of the code.	7
	Use lazy formatting in the logger to defer string interpolation until necessary Use lazy formatting in the logger to defer string interpolation until it is necessary, which can improve performance when logging is disabled or set to a higher level. pr_agent/git_providers/github_provider.py [150] -get_logger().info(f"Skipping a non-code file: {file.filename}") +get_logger().info("Skipping a non-code file: %s", file.filename) Suggestion importance[1-10]: 6 Why: Using lazy formatting for logging can save computational resources when the log level is set such that the message would not be logged. This is a valid improvement, especially for scenarios where logging is intensive or conditional.	6