Our tool relies on data fetched from your repositories to evaluate the productivity of your engineering team effectively.

In this guide, we will walk you through the process of connecting your Git providers, explain the types of data we fetch, and provide solutions to common connection issues.

​
Importance of Connecting Git Providers

To evaluate productivity, our tool analyzes data from your commits in Git repositories. Connecting your Git providers such as GitHub, GitLab, Bitbucket, and Azure allows our tool to access this vital data. By integrating these providers, you enable our tool to fetch and analyze commits, providing valuable insights into your engineering team’s productivity.

​
Supported Git Providers

We support the following Git providers:

  • GitHub

  • GitLab

  • Bitbucket

  • Azure DevOps

​
Inviting Team Members

Admins can invite other users to help connect Git providers if needed. For instructions on sending invites and understanding user roles, please refer to the Settings and User Roles Overview pages.

​
How to Connect Each Git Provider

​
GitHub

​
Connecting via API Token

Please refer to GitHub documentation for more detailed instructions: Managing your personal access tokens - GitHub Docs

Note: When selecting a personal access token, please follow the instructions for generating the token via the classic path—‘Tokens (classic).’

1

Generate an API Token

Go to your GitHub account settings, navigate to “Developer settings,” and select “Personal access tokens.” Click on “Generate new token.”

2

Choose the expiration period

In the Expiration field, choose the “No expiration” option to avoid any disruptions. If you decide to disconnect your Git provider, you can easily do so on the Connections page.

3

Select Scopes

Ensure you select the appropriate scopes, particularly repo, read:user, user:email to allow access to your repositories.

4

Copy the Token

Once generated, copy the token.

5

Connect in Our Tool

Go to our tool’s Connections page, select “Connect” next to the GitHub’s logo and paste the API token. Please enter your username/handle in the ‘Username’ field and your organization in ‘Organization’ as specified in GitHub.

You should now be successfully connected to the tool and see the name of your organization along with the number of connected repositories on the page.

​
GitLab

Please refer to GitLab documentation for more detailed instructions: Personal Access Tokens

1

Generate a Personal Access Token

Go to your GitLab account settings, navigate to “Edit profile”, then “Access Tokens,” and create a new token.

2

Select Scopes

Ensure you select the api and read_repository scopes.

3

Copy the Token

Once generated, copy the token.

4

Connect in Our Tool

Go to our tool’s Connections page, select “Connect” next to the GitLab’s logo and paste the access token.

​
Bitbucket

Please refer to Bitbucket documentation for more detailed instructions: Create a Repository Access Token | Bitbucket Cloud | Atlassian Support

1

Choose What to Connect

In Bitbucket, you can connect a repository, a project, or the entire workspace. For our tool, please create a token to grant access to the repository.

2

Navigate to Settings

Choose the settings on your Bitbucket profile, then navigate to “Security.”

3

Access Tokens

Click on “Access tokens” to create a new token.

4

Create Access Token

Ensure you select the repository scope > Repository read as well as webhook scope > Webhook Read and Write. Once done, press “Create” and copy the generated key.

5

Connect in Our Tool

Go to our tool’s Connections page, select “Connect” next to the Bitbucket’s logo and paste the access token.

​
Azure DevOps

Please refer to Azure Git documentation for more detailed instructions: Use Personal Tokens

1

Generate a Personal Access Token

Go to your Azure DevOps profile, navigate to “Personal access tokens,” and create a new token.

2

Select Scopes

Ensure you select the code scope > Read.

3

Copy the Token

Once generated, copy the token.

4

Connect in Our Tool

Go to our tool’s Connections page, select “Connect” next to the Azure’s logo and paste the access token.

​
Data Fetched from Git Providers

Once connected, our tool fetches the following data from your private repositories:

  • SHA: Unique identifiers for each commit.

  • Contributor Information: Names of contributors/usernames.

  • Contribution Data: Metrics on how much each contributor has contributed.

  • Commit Timestamps: Information on when contributions were made.

  • Branch Information: Details about the default main branch in your repositories.

This data is crucial for analyzing the productivity and contribution patterns of your team. For more information, please read about what our tool collects and stores here.

​
Viewing Connected Providers

After successfully connecting a Git provider, you will see the connection listed on the settings page, along with the number of repositories connected.

​
Multiple Git Providers

You can connect multiple Git providers simultaneously. This allows our tool to aggregate data from various sources, providing a comprehensive analysis of your team’s productivity.

​
Common Connection Issues

If you encounter issues while connecting a Git provider, consider the following possibilities:

  • Invalid or expired tokens

  • Insufficient permissions or scopes selected

  • Network or connectivity issues

  • Restrictions from the Git provider’s side

  • The organization name entered in our tool does not match the name in the Git provider, or the organization’s name has been changed in the Git provider

  • The connected repositories contain code written in a programming language, framework, or tech stack not supported by our tool

Please note that we only support the following languages and frameworks:

PHP, Python, JavaScript (ReactJS, React Native, TypeScript, ECMAScript), Objective-C, Swift, Go, Ruby, Java (including Java for Android), .NET (C#, ASP.NET).

Only private repositories are fetched and analyzed to ensure the confidentiality and relevance of the data.

Contact us at support@p10y.com.