Set a Title in the Browse GitHub picker but no heading appears on the page

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

What you are seeing

I set a Title in the Browse GitHub picker but no heading appears on the page.

The preview step of the file picker, with a Title field containing sequence.mermaid above a rendered Mermaid sequence diagram of a user sign up flow, and an Add to page button in the bottom corner.
The Title box sits above the preview and is filled with the file name until you type something else.

#Why it happens

The title is collected and stored but never rendered. The macro header always shows owner/repo/path instead.

#What to do

Do not rely on the Title field. If you need a heading, add a normal Confluence heading above the macro.

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

#Limits that apply here

Limit

Value

What happens

Auto-convert: only two hosts

-

Github.com blob links and raw.githubusercontent.com links only. Directory (tree/) links, gists and GitHub Enterprise hosts do not convert.

Connect polling gives up after 30 seconds

-

-

No caching of file content

-

Every render of a GitHub-file macro re-fetches the file. A page with many GitHub macros consumes GitHub API budget on every view.

#A few things that catch people out

  • Three of the four settings a user could plausibly reach do nothing useful: Show Line Numbers is completely inert (and line numbers are permanently on), Title is stored but never displayed, Description is never even collected, and Show Border only affects the empty and error states. Only document these with an explicit note about what they actually do, or the documentation ships four user-facing un

Found it? Good.