At a glance
| Input | Current action | Output | Boundary |
|---|---|---|---|
| Approved GitHub repository | Configure Repository, Confluence space, and Allowed paths | Report-only terminology scan scope | The connector checks terminology. It does not create enterprise trace evidence. |
| Connector scan | Select Scan by request | Recent asynchronous jobs and Git terminology findings | Source excerpts and file contents are not rendered in the connector UI. |
| Undefined Git finding | Select Add as draft | Draft glossary term | This starts terminology governance, not trace-link approval. |
| Immutable Git SHA and bounded code or test files | Call the backend evidence mapper | Artifacts, revisions, subjects, usages, and candidate links | Production connector resolvers do not call this mapper. Its direct coverage is code and tests. |
| Declared implements or verifies relationship | Normalize the declaration | Link with candidate approval state and immutable provenance | Candidate links are review-only. They are excluded from governed traversal. |
| Approved or imported trace nodes and links | Expand indexed neighbors in both directions | Forward and reverse graph hops | Candidate links and unapproved endpoints are excluded. Missing or truncated evidence creates coverage blockers. |
| Enterprise evidence workspace | View Trace graph, Forward impact, and Reverse provenance | Visible graph area | Current UI requests omit a start node. Selecting evidence does not reload the graph with one. |
How it works
- Open Git Connector as an administrator.
- Set Repository, Confluence space, and Allowed paths.
- Select Save connection.
- Select Scan by request for a report-only terminology check.
- Review Recent asynchronous jobs and Git terminology findings.
- Use Add as draft only for an undefined glossary term. It does not approve a trace link.
- Do not present this connector workflow as governed GitHub-to-Confluence traceability.
Example
A connector scan can flag a deprecated term in an approved repository. Separate mapper code can normalize one function and its test. It can emit implements and verifies candidates against requirement nodes. Those candidates remain outside governed traversal. Production version 6 has no visible candidate-review or approval control.
What this does not mean
Production version 6 deploys the GitHub web trigger, scan consumer, connector resolvers, and GitHub API egress. These components support report-only terminology checks. The enterprise mapper and indexed trace services are implemented and tested separately. The connector does not invoke the mapper. The workspace exposes trace controls, but its client does not request graph expansion from a selected node. Only approved or imported links qualify as governed evidence.
Related questions
Next step
Use Git Connector for terminology checks. Do not rely on it as an end-to-end GitHub-to-Confluence evidence trace.
View on Atlassian Marketplace