Repository navigation
Conversation
mwolson
force-pushed
the
contrib/mobile-thread-context-id
branch
from
October 22, 2026 03:11
f48ec27 to
da05a6d
Compare
mwolson
force-pushed
the
contrib/sso-pr-media
branch
from
October 22, 2026 03:11
978f34e to
b949423
Compare
mwolson
force-pushed
the
contrib/sso-pr-media
branch
2 times, most recently
from
October 24, 2026 00:11
e7e89c0 to
ea8a3d1
Compare
mwolson
force-pushed
the
contrib/mobile-thread-context-id
branch
from
October 24, 2026 00:38
7686216 to
ea436c2
Compare
mwolson
force-pushed
the
contrib/sso-pr-media
branch
from
October 24, 2026 00:38
ea8a3d1 to
94edaf8
Compare
mwolson
force-pushed
the
contrib/sso-pr-media
branch
from
October 24, 2026 16:10
94edaf8 to
b4ad4fd
Compare
Carries pingdotgg#19191 sso-pr-media by cbangera2, adapted to the GitHub source-control driver's media fetch. When github.com answers an upload fetch with its SSO sign-in page, the driver renders the upload through the markdown API, which honours the SSO-authorized token and returns a signed private-user-images URL, then fetches that URL without the token. The media request now carries the checkout, so an upload without a repository in its URL is rendered with the checkout's own GitHub repository as context. Drop this layer at the refresh after pingdotgg#19191 sso-pr-media merges upstream.
mwolson
force-pushed
the
contrib/mobile-thread-context-id
branch
from
October 29, 2026 11:33
20e327e to
d868d3f
Compare
mwolson
force-pushed
the
contrib/sso-pr-media
branch
from
October 29, 2026 11:33
b4ad4fd to
ad7b077
Compare
Owner
Author
|
Dropped in the 2026-11-09 refresh: upstream pingdotgg#21632 (a09aef3) loads PR uploads from SSO organizations with the same design. |
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.
What Changed
Carries pingdotgg#19191 sso-pr-media by cbangera2, adapted to the GitHub source-control driver's media fetch. When github.com answers a pull request upload with its SAML SSO sign-in page, the driver renders the upload through the markdown API, which accepts the SSO-authorized token and returns a signed
private-user-imagesURL, then fetches that URL without the token. The media request now carries the checkout, so an upload whose URL names no repository is rendered with the checkout's own GitHub repository as context, including a project rooted at a bare clone. Signed URLs are cached for four of their five minutes so video seeks reuse them. Organizations without SSO make no extra requests.Why
Images and videos in pull request descriptions from SSO-enforcing organizations show "Image unavailable" in the PR panel. Drop this layer at the refresh after pingdotgg#19191 sso-pr-media merges upstream.
Checklist