GitHub search fields
GitHub writes 6 fields into Confluence's own search index. Once a page has been indexed you can filter and sort by them in Capable Search, and use them in ordinary Confluence CQL.
A page Confluence has not indexed yet carries no values at all. It does not match a query on these fields, and it does not come back as an empty result either. On a large site indexing takes hours to days to catch up.
The <hash> prefix is your installation's app hash. Field names are written with it, so the exact string differs per site. Use the Copy CQL action in the search table rather than typing it.
#The fields
Field | What it holds |
|---|---|
Git File Count / Git Repositories / Git File Types / Git Organizations / Git Last Updated | Match pages by embedded Git content, file count, repo, file type, organisation, last update. |
<hash>_git_count | Total number of GitHub files referenced on the page. Example: `<hash>_git_count >= 5`. Note the alias drops the `capable_refs_` middle: it is `<hash>_git_count`, not `<hash>_capable_refs_git_count`. |
<hash>_git_repos | GitHub repository "owner/name" referenced by a file on the page. Example: `<hash>_git_repos = "capable-software/capable-repo"`. |
<hash>_git_orgs | GitHub organisation/owner referenced by a file on the page (the part before the slash in repos). |
<hash>_git_file_types | File-type of GitHub files referenced on the page, derived from the extension. Example values "ts", "py". |
<hash>_git_updated | BROKEN BY TYPE MISMATCH. The field is offered as a number but is filled with a date written as text. A string value cannot be extracted into a numeric alias, |
#Related
Indexed, then searchable. In that order.
