Repository navigation
feat(hub): recover after GitHub App transfers - #62
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep transfer recovery and critical failure coverage while removing duplicate scenarios, unlikely response variations, and internal-step assertions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Check repository availability instead of counting GitHub requests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nshki
approved these changes
Oct 21, 2026
nshki
left a comment
nshki
left a comment
Contributor
There was a problem hiding this comment.
Confirmed in a separate staging environment.
alliscode
reviewed
Oct 22, 2026
Bind branch and workflow discovery writes to the owner and installation captured before GitHub work, including webhook receipts and missing-run results after repository reactivation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retain the latest schema version alongside the installation-account migration, and preserve main's administration continuation and Storybook changes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nshki
approved these changes
Oct 22, 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.
Why
Hub operators currently need console edits after transferring their GitHub App to another account. Hub should update the owner itself and restore repository access once the new owner reinstalls the same App. Fixes #61.
What changes
Hub stores the installation account separately from the App owner. Its existing scheduled checks and installation notifications confirm the current owner through GitHub and recognize a replacement installation. This also recovers transfers completed before upgrading Hub. The administration page explains when reinstallation is needed, and the setup guide describes the recovery flow.
Polling and push or workflow notifications cannot save branch and workflow results from a previous owner or installation, even after the same repository becomes available again. This includes branch deletion and missing-workflow results.
Repository access pauses while the App is uninstalled. Existing Builds, reviews, users, browser Sessions, and canvas grants remain, but repository access still requires a verified installation in the current App owner's account. No audit-log permission or cross-account installation support is added.
Recovery after transfer and reinstallation was confirmed in a separate staging environment before this follow-up.
The merged full Rails run returned HTTP 503 in unchanged learning-recall coverage. That file passed when rerun on its own, but combined-suite stability remains unverified.
Storybook screenshots
Hub/Pages/Security/GitHub App / Installation Required - light theme, 1440 x 1000 viewport.