GitHub

Our GitHub integration collects metadata about your organization’s activity across repositories, pull requests, and deployments. We never read, transmit, or store source code. Sensitive data, such as branch names and pull request titles, are always encrypted.

Permissions

We request only the necessary permissions to analyze Git metadata. Below is a description of the scopes requested when connecting to GitHub: 

• Repository: Read access to actions, checks, code, commit statuses, deployments, issues, metadata, and pull requests
• Organization: Read access to members, organization administration, organization copilot seat management, and organization projects
• User: Read access to email addresses, public repositories, public organization information, and public user profile data

We require read access to metadata for commits, branches, and releases. Since GitHub’s API does not offer more granular permissions for these specific endpoints, we must request read access to all repository contents. Please note that we never read, transmit, or store source code.

You can learn more about permissions for GitHub Apps in GitHub’s documentation. 

Requesting App Access

Creating a Software organization requires a GitHub organization. By default, OAuth app access restrictions are enabled for GitHub organizations: 

When OAuth app access restrictions are enabled, organization members and outside collaborators cannot authorize OAuth app access to organization resources. Organization members can request owner approval for OAuth apps they'd like to use, and organization owners receive a notification of pending requests.

If you do not see your GitHub organization when trying to create a Software organization, you will need to request that an organization admin approves the Software application for use in your organization. 

You can request access from your GitHub account, or follow GitHub’s guide on how to request OAuth app access. An organization admin will then need to approve the request.