Where connecting is possible
Only from a GitHub-file macro on a page, or from the macro's Browse GitHub configuration modal. Both run on the `resolverAuthed` function, which is the only function that declares providers.auth: github.
#Where you do it
Task | Where |
|---|---|
Connect your GitHub account | On a Confluence page: insert the "Github file (Capable)" macro, then press Connect GitHub in the macro; or open the macro's configuration and press Connect in the Browse GitHub modal. |
Add a file from a repository to a page | Macro configuration → Browse GitHub modal |
Add a file without opening the picker | The Confluence editor |
#Settings that affect this
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 |
|---|---|---|
No rate-limit handling anywhere | - | There is no retry, no backoff and no Retry-After handling in the capability. A GitHub 403 caused by rate limiting is classified as an access error and reported to the reader as though nobody has acces |
#Related
Better with company.
