Pull requests inbox shows stale check/review state (does not update after re-runs or long checks) #213479
Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The pull requests inbox at github.com/pulls/inbox puts some of my PRs in the wrong section, and they stay there after the PR's real state changes. The PR page and the GraphQL API report the correct state. The inbox and issue search do not. Both cases below are in private org repos, so I've left out the links.
Case 1: shown as "checks failing" after a re-run passed
completed/success.Issue search agrees with the inbox.
is:pr is:open author:@me status:failurestill returns this PR, six days after the re-run passed. The search index appears to record the first attempt's failure and never update after a re-run on the same SHA.Case 2: shown as "waiting for reviews or checks" when it's ready to merge
GraphQL reports
reviewDecision: APPROVEDandmergeStateStatus: CLEAN, and the merge button is green. The inbox lists the PR under "waiting for reviews or checks". Search returns it forstatus:pendingand not forstatus:success. Other PRs in the same repo with the same set of app check suites (a few third-party apps that leave a queued suite with no runs) show asstatus:success, so those suites don't seem to be the cause. My guess is that the index recorded the checks as pending while the long deploy job ran and never updated when it finished.Expected
The inbox section and the
status:/review:search qualifiers should match what the PR's merge box shows, including after workflow re-runs and after long-running checks complete.All reactions