Working with other capabilities
Most of what makes GitHub worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.
Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.
#Every connection
Connects to | What you get |
|---|---|
Authentication model | Everyone connects their own GitHub account. Connections belong to the person, not to your Confluence site, so there is no shared GitHub App and no shared service account. |
OAuth scopes requested | Repo, user:email, read:org, read:user |
Consent behaviour | GitHub shows its consent screen every time you connect, even if you have already authorised the app. |
Connect flow | - |
Where connecting is possible | Only from a GitHub file macro on a page, or from the macro's Browse GitHub window. |
Connected account identity | Your GitHub username and avatar are shown, so you can see which account is connected. |
Connection health checking | Capable checks with GitHub that your connection still works, so a revoked or expired token shows as not connected. |
Revocation | When you unlink the app in Atlassian's Connected Apps settings, the access token is revoked with GitHub. |
Public file path (no connection needed) | Capable tries to fetch a public file without any sign-in first. This is how logged-out and unlicensed readers see public files. |
Private file path | Capable tries the configured account and a public fetch, then every other GitHub account you have connected, and only then offers to connect. Logged-out readers are never asked to connect. |
Network destinations | Files are read from https://raw.githubusercontent.com and avatars come from https://avatars.githubusercontent.com. |
Server functions that talk to GitHub (nine) | Nine background functions handle connecting, listing your accounts, repositories, folders, files and branches, and checking that your connection still works. |
Repository listing | The picker lists repositories you own, collaborate on or belong to through an organisation, newest activity first, with private repositories always at the top. Public repositories you do not belong to can only be found through search. |
Search fields written per page | Pages with GitHub macros are indexed so you can search by details such as the number of GitHub files, the repositories used and the file types. |
#A few things worth knowing
A connection needs both halves installed. In a standalone app most of these do not exist.
Anything that depends on search only reflects pages that have been indexed.
Published sites render Capable macros properly, which is where several of these pay off.
#Related
Better with company.
