At a glance
| Input | Current action | Output | Boundary |
|---|---|---|---|
| Approved GitHub repository | Configure Repository, Confluence space, and Allowed paths, then Save connection | Report-only terminology scan scope | The connector checks terminology. It does not create trace evidence. |
| Connector scan | Select Scan by request | Recent asynchronous jobs and Git terminology findings | Scans run by request only. Source excerpts and file contents are not shown. |
| Undefined Git finding | Select Add as draft | Draft glossary term | This starts terminology review, not trace-link approval. |
| GitHub file, commit, or test URL | Declare trace node with type code_reference or test and External reference or URL | Candidate node | The app stores the reference. It does not fetch or hash the GitHub revision. |
| Code or test node and a requirement node | Declare trace link with relation implements or verifies | Candidate link | Candidates are excluded from traversal. |
| Candidate node or link | Another administrator selects Approve with a Review reason | Governed node or link | The declaring administrator cannot approve their own declaration. |
| Approved start node | Choose it in Start node, then select Show trace graph | Forward impact and Reverse provenance hops | Workspace default 5 hops and 200 links. |
How it works
- Open Git Connector as an administrator and set Repository, Confluence space, and Allowed paths.
- Select Save connection, then Scan by request for a terminology check.
- Review Git terminology findings. Use Add as draft only for an undefined glossary term.
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- Use Declare trace node for each GitHub code reference or test, with its URL in External reference or URL.
- Use Declare trace link to connect each node to its requirement node.
- Ask another administrator to approve in Trace nodes awaiting approval and Trace links awaiting approval.
- In Trace graph, choose the requirement in Start node, select Show trace graph, then Forward impact.
Example
A connector scan flags a deprecated term in an approved repository. Separately, an administrator declares a code_reference node for one function and a test node for its test, both with GitHub URLs. Another administrator approves the nodes and their implements and verifies links. Forward impact from the requirement then shows both hops.
What this does not mean
Production deploys the GitHub web trigger, scan worker, connector resolvers, and GitHub API egress for terminology checks. The production GitHub App has no webhook, so scans run by request. Backend code that maps GitHub revisions into trace evidence exists, but nothing in production calls it. Trace nodes hold the reference you enter, not a captured GitHub revision.
Related questions
Next step
Use Git Connector for terminology checks. Declare and approve trace nodes and links to connect GitHub work to Confluence requirements.
View on Atlassian Marketplace