Readers see "Connect a GitHub account with access to this repository to view this file"

What you are seeing

Readers see "Connect a GitHub account with access to this repository to view this file".


#Why it happens

The file is in a private repository and that reader has no connected GitHub account that can reach it. Access is always per-person; there is no site-wide or admin-level GitHub connection.


#What to do

Each reader presses Connect GitHub in the macro and authorises their own GitHub account. If they have several accounts, they can add more. The macro automatically tries all of them.


#Settings involved

Setting

Where

What it does

There is no GitHub settings screen

Nowhere

The git capability declares no global settings tab and no space settings tab, so GitHub contributes nothing to Capable global settings or space settings. There is also no admin "connect the site to GitHub" screen, becaus

Hide GitHub across the whole site

App property `capable-global-hidden-capabilities`, object name `hiddenCapabilities`, value

Hides the capability tenant-wide. IMPORTANT: this gates the BYLINE ONLY. The macro module has no display conditions, so hiding the capability does not stop existing GitHub macros from rendering on pages.

Turn GitHub on or off per space

Space property `<APP_HASH>_capable`, object name `capabilities.alwaysOff` / `capabilities.

AlwaysOff suppresses the byline in that space; alwaysOn shows it even on pages with no GitHub macro. Again, byline only. Macros still render.


#Limits that apply here

Limit

Value

What happens

Auto-convert: only two hosts

-

Github.com blob links and raw.githubusercontent.com links only. Directory (tree/) links, gists and GitHub Enterprise hosts do not convert.

Connect polling gives up after 30 seconds

-

-

No caching of file content

-

Every render of a GitHub-file macro re-fetches the file. A page with many GitHub macros consumes GitHub API budget on every view.



Found it? Good.