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" where a GitHub file should be.


#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 tries all of them automatically.


#Settings involved

Setting

Where

What it does

There is no GitHub settings screen

Nowhere

GitHub adds nothing to Capable global settings or space settings, and there is no admin "connect the site to GitHub" screen. Each reader connects their own account from the macro.

Hide GitHub across the whole site

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

Hides the page byline across the whole site. This affects the byline only. Existing GitHub macros keep showing their files.

Turn GitHub on or off per space

Space property <APP_HASH>_capable, object name capabilities.alwaysOff or capabilities.alwaysOn

alwaysOff hides the byline in that space. alwaysOn shows it even on pages with no GitHub macro. Again, byline only. Macros still show their files.


#Limits that apply here

Limit

Value

What happens

Pasted links: only two hosts

-

Only github.com file links and raw.githubusercontent.com links turn into a macro. Folder (tree/) links, gists and GitHub Enterprise hosts do not.

Connecting waits 30 seconds

30 seconds

If you have not finished connecting after 30 seconds, Capable stops waiting. Press Connect GitHub again.

Files are fetched on every view

-

Each time a page loads, every GitHub file macro fetches its file again. A page with many GitHub macros uses more of your GitHub API allowance on every view.



Found it? Good.