Understand repository scope and indexing for Code Context

Summary

Users often require clarification on how Code Context handles repository allowlists, branch indexing, data residency, and user permissions when integrated with GitHub.

This article provides answers to common questions regarding repository scope, indexing, and compliance for the Code Context feature.

Solution

Code Context provides AI-powered insights by indexing your source code. Review the following details to understand how the feature manages data and permissions.

Repository scope and allowlists

Code Context strictly inherits its repository scope from the GitHub for Atlassian connector. The feature only indexes repositories provided in the connector's subscription list. Any repository that is disabled or omitted in the connector is ignored and will not be indexed. Currently, there is no separate or independent repository allowlist specifically for Code Context.

Branch and tag indexing

To maintain performance and relevance, Code Context only indexes the default branch (typically main or master). Secondary branches and tags are not indexed at this time.

Data residency and compliance

Code Context data is stored in the US region. Please note that the feature is not HIPAA-compliant at this time. Ensure your organization's data policies align with these specifications before use.

User permissions at query time

Security is maintained through real-time permission checks. Results are only returned if GitHub verifies that the querying user has active permissions to view the specific repository. If a user loses access to a repository in GitHub, they will no longer see results from that repository in Code Context.