Capable → Github catalogue page

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

A section in the Capable app, titled "Github", subtitled "Add files from GitHub repositories to pages", order 50. It has FOUR groups: Getting started (dismissable), "All files" browse view, a Browse-by-file-type heading with 8 sub-sections (including an image sub-section), and an "About" heading containing the roadmap/changelog section.

The Capable app with the Github tab selected, showing a table of four Confluence pages with columns for title, space, files, repositories and organisations, and a right hand panel for the selected pag
Every page holding a GitHub file is listed with its space, its file count and the repositories it draws on, and selecting a row lists the files themselves.

#Worth knowing

Every view queries the Confluence content index via CQL. It never talks to GitHub. The roadmap section is wired with capabilityKey 'git', changelog tag 'github', roadmap column '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.

#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.

How it actually behaves.