GitHub settings
GitHub does not have a settings tab of its own. It is configured from the shared Capable settings instead. This is the complete list.
#Every setting
Setting | What it does |
|---|---|
There is no GitHub settings screen | GitHub adds nothing to Capable global settings or space settings. There is also no admin "connect the site to GitHub" screen. |
Hide GitHub across the whole site | Hides GitHub for the whole site. This affects the byline only. Hiding GitHub does not stop existing GitHub macros from showing on pages. |
Turn GitHub on or off per space | alwaysOff hides the byline in that space. alwaysOn shows it even on pages with no GitHub macro. Again, this affects the byline only. Macros still show. |
Edition and feature flags | GitHub is part of the Standard edition, so it is included in both Standard and Advanced. It is not behind a feature flag. |
Unlicensed and anonymous access | Granted to the macro only, for readers without a licence and for logged-out readers. They still see public file content in a read-only view. |
Byline visibility conditions | The reader must be logged in with permission to view the page. Then one of these must also be true: the space has alwaysOn set, the page already has stored GitHub data, or the GitHub macro appears in the page's Capable content index. |
#A few things worth knowing
Settings changes can take a minute to reach other people.
Hiding a capability removes it from the navigation. Macros already on pages keep showing.
Some settings are per space and need only a space administrator.
#Related
The complete list, in one table.
