Explain why reactions don't save for enterprise-managed (EMU) accounts - #509
Merged
soyalejolopez merged 2 commits intoAug 3, 2026
Merged
Conversation
EMU accounts can read public repos but GitHub blocks them from reacting to or commenting on anything outside their enterprise, so a giscus vote optimistically renders and then vanishes on reload. Nothing repo-side can grant them access. Adds a standing sign-in note under Community & upvotes, and escalates it to a warning naming the account when giscus metadata reports an enterprise-managed viewer (underscore in the login, which is illegal in regular github.com usernames). Turns on data-emit-metadata for read-only viewer detection; deliberately still no remount. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9bba8d74-291d-45ee-8546-18ae94ace744
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
2 participants
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
Reactions on the site silently fail for anyone signed in with an enterprise-managed GitHub account (EMU). The 👍 renders optimistically, then the count reverts on reload, so it looks like the site is broken.
Why
It is not a giscus or repo bug. GitHub blocks managed user accounts from interacting with repositories outside their own enterprise, including adding reactions and creating or commenting on discussions. They can read this repo just fine, which is what makes it confusing.
Reference: Abilities and restrictions of managed user accounts → Interactions
There is no repo-side or org-side setting that grants these accounts access. It is a platform restriction on the user, so the only fix available to us is making the failure legible.
Changes
name_companyaccounts can read but not react, with a link to the GitHub doc.data-emit-metadatais turned on purely to readviewer.loginfrom giscus. An underscore in a login is a reliable EMU signal, since regular github.com usernames cannot contain one. When detected, the note turns amber, names the signed-in account, and states plainly that the vote will look saved and then disappear, along with the workaround (personal github.com account, incognito window).Deliberately not doing
No iframe remount. The
emit-metadatalistener is read-only. PR #505 removed a metadata-driven remount that was destroying reactions server-side by tearing down the iframe mid-mutation, and that warning comment is left intact directly above this code.Validation
Served locally against live giscus. Notice renders correctly in both light and dark themes, the EMU escalation path was exercised directly, and the page loads with zero console errors.