Merged
Conversation
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Mar 16, 2026
k11kirky
approved these changes
Mar 16, 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.

Problem
The GitHub integration service had a whole callback server (HTTP in dev, deep links in prod) to detect when the user completed the OAuth flow. This was overly complex and fragile - it managed sockets, timeouts, and HTML responses just to know "did the user click authorize."
Changes
GitHubIntegrationService- now it just opens the authorize URL in the browser and returns immediatelyintegration-flow-schemas.tsso Linear (and future integrations) can reuse themGitIntegrationStepto poll for the integration instead of waiting for a callbackcancelFlowendpoint since there's nothing to cancel anymore