# Page byline: "Github (Capable)" A byline item on the page, tooltip "Add files from GitHub", that lists the GitHub files on the page and shows a count badge ("1 file" / "N files"). Clicking through links out to github.com/{owner}/{repo}/blob/{branch}/{path}. --- ## Worth knowing When the page has no parseable git macro, a dedicated empty state is shown. --- ## Where you do it ![](https://help.gocapable.com/images/a0886c98-6c7f-4669-99d0-a692ea0b9766.webp) The count beside the git icon tells readers how many GitHub files the page holds, here next to a PNG rendered straight from a repository. | **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 \`\_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. | --- ## Worth knowing * Hiding the capability (site-wide or per space) gates the byline ONLY. The macro module has no display conditions, so existing GitHub macros keep rendering. * The macro is a live window on GitHub, not a snapshot. Content is re-fetched on every view with no caching, which is both a freshness feature and a performance and rate-limit liability. --- ## Related [Capable → Github catalogue pageAnother part of how this works.](https://help.gocapable.com/git/capable-github-catalogue-page.html) [Capable Search integrationAnother part of how this works.](https://help.gocapable.com/git/capable-search-integration.html) [How it worksThe rest.](https://help.gocapable.com/git/how-it-works.html) --- _How it actually behaves._