At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Approved repository and paths | Save the connector configuration | Bounded source scope | Administrator access is required |
| Immutable Git revision | Fetch supported allowed files | Revision-bound scan job | Provider access and batch limits apply |
| Approved Confluence glossary policy | Compare repository terminology | Report-only findings | Findings do not edit code or approve terms |
| Later source or policy change | Run another scan | New job and result | Earlier results remain tied to their revision |
How it works
- Open Git Connector.
- Enter Repository, Confluence space, and Allowed paths.
- Select Save connection.
- Use Scan by request.
- Review Recent asynchronous jobs.
- Review Git terminology findings and correct the owning source.
Example
A repository still uses a deprecated incident label at one commit. The GitHub terminology scan records a report-only finding with revision context. The code owner changes the source. A later scan evaluates the new commit separately.
What this does not mean
The visible connector scans terminology. It does not write to GitHub, approve code, create release evidence automatically, or expose an end-to-end code-to-requirement trace workflow.
Related questions
Next step
Use immutable revisions and narrow allowed paths for every repository scan.
View on Atlassian Marketplace