fix: show UNKNOWN in status when a PR's live state cannot be fetched - #120
Merged
Conversation
|
Warning Review limit reachedNext included review available in 46 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
# Conflicts: # tests/test_cli_coverage.py
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
statusfell back to the recordedPRRecord.statewhenever the livegh pr viewlookup returned nothing. That recorded state is never written back aftermerge/clean, so it is alwaysopen— a merged, closed, or deleted PR (or any run with gh unauthenticated) was shown as a confidentOPENwith no hint that the fetch had failed.Now an unfetchable PR renders
UNKNOWNand a yellow line after the table lists the affected PR numbers with a pointer togh auth status. README's status paragraph documents this.Test plan
test_unfetchable_state_is_unknown_not_open(one PR{}, oneMERGED):UNKNOWNandMERGEDshown, noOPEN, warning names#7— fails on main withOPENtest_live_state_and_review_are_shown: normal path unchanged, no warning