Symptom
Merged PRs no longer transition to the purple ("merged") state during the periodic polling of GitHub issues. They only update on application open.
Possibly related log error
This error appears in the logs and may or may not be related:
[IssueTracker] Stale-PR follow-up failed (exit 1): gh: Could not resolve to a Repository with the name 'big-bang/product'.
big-bang/product is a GitLab repo in the PlatformOne workspace (host repo1.dso.mil), so invoking gh for it would always fail. If the periodic stale-PR follow-up bails on the first error per cycle, that could explain why none of the other merged PRs get re-checked between app launches.
Asks
- Diagnose why the periodic poll no longer flips merged PRs to purple (regression vs. open-time path).
- Diagnose the
gh invocation against a GitLab repo — should be routed through glab (with GITLAB_HOST=repo1.dso.mil) instead.
- Confirm whether the two are the same root cause or independent.
Symptom
Merged PRs no longer transition to the purple ("merged") state during the periodic polling of GitHub issues. They only update on application open.
Possibly related log error
This error appears in the logs and may or may not be related:
big-bang/productis a GitLab repo in the PlatformOne workspace (hostrepo1.dso.mil), so invokingghfor it would always fail. If the periodic stale-PR follow-up bails on the first error per cycle, that could explain why none of the other merged PRs get re-checked between app launches.Asks
ghinvocation against a GitLab repo — should be routed throughglab(withGITLAB_HOST=repo1.dso.mil) instead.