On a published Capable Site the file is replaced by an amber note
What you are seeing
On a published Capable Site the file is replaced by an amber note.
#Why it happens
Deliberate. The file is read through an authenticated GitHub connection belonging to a person in your tenant, and a published site has no access to that.
#What to do
Nothing to fix. This is by design. Put the content directly in the page if it needs to appear on a published site.
#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. |
#Related
Found it? Good.
