Workflows view shows stale data after switching GitHub accounts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- electron, github, github-actions, react, typescript
- Domain
- authentication, ci-cd, desktop, frontend
Research direction
Start by tracing the account-switching UI and the Workflows tab's workflow-run loading and selected-repository state. Reproduce the switch between two gh CLI accounts, then verify that inaccessible repository data is cleared, replaced with a repository-selection prompt, or reported as an error rather than remaining visible.
Written by the indexing model from the issue text.
Description
Description
When multiple GitHub accounts are configured via gh CLI, switching accounts from the UI does not refresh the workflows view. If a private repo was selected under account A, switching to account B (which has no access to that repo) still shows stale workflow runs from account A's private repo instead of clearing or showing an error.
Steps to Reproduce
- Have multiple GitHub accounts logged in via gh CLI
- Select a private repo under account A
- Go to the Workflows tab - runs load fine
- Switch to account B from the UI (account B has no access to account A's private repo)
- Workflows tab still shows runs from account A's private repo
Expected Behavior
Switching accounts should refresh the workflows view. If the currently selected repo is not accessible under the new account, the app should either clear the view, prompt to select a new repo, or show an appropriate error.
Actual Behavior
Stale workflow data from the previous account's inaccessible repo persists in the UI after switching accounts.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from binbandit/dispatch
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in binbandit/dispatch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·