Repository navigation
Document temporary gh-agent file-mode workaround - #844
Merged
Merged
Conversation
nateberkopec
added a commit
that referenced
this pull request
Oct 5, 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.
This is AI-assisted. Model: gpt-6.1-sol
Refs #843. Keep the blocked issue open until the hosted upstream fix is verified and the workaround is removed.
Record the immutable gh-agent app commit/deployment, the mode-only repair used to unblock #842, test evidence, known limits, and return-to-upstream conditions.
The native operation is already deployed and tested: 19 app tests passed (including workerd), strict TypeScript check passed, saved source bytes match tested files, and live repair/idempotence checks passed. No account or runtime dependency changes.
This uses option 2’s hosted-app revision instead of a patch-version upstream fork release. The docs state explicitly that there is no managed-installer pin and that the normal fix-upstream release/installation gates are not completed. No convergence was run.