fix: add PR number context to file-content fetch failure warning#711
Merged
anderdc merged 3 commits intoentrius:testfrom Apr 23, 2026
Merged
Conversation
anderdc
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pr_numbercontext to the existing warning in_fetch_file_contents_with_base_batchwhen file-content GraphQL fetch returnsNone.pr.numberfrom scoring intofetch_file_contents_with_base(...)so logs identify the exact failed PR.Nonevs[]return-contract changesRelated Issues
Closes #710
Supersedes #645
Type of Change
Testing
Tests added/updated
Manually tested
Ran:
uv run pytest tests/utils/test_github_api_tools.py tests/validator/test_base_score.pyResult:
82 passedChecklist