Here, you will find comprehensive information about all the repositories that have been successfully fetched after connecting your Git providers.

​
Repository Information

After establishing a connection with your Git providers, our tool collects essential data from your repositories. Below are the key pieces of information displayed for each repository:

  • Repository Name: The name of the fetched repository.
  • Project: The name of the project that this repository is part of.
  • Branch: The branch from which the data is being fetched, ensuring you are working with the latest changes.
  • Technology: The primary technology or programming language used in the repository, allowing you to gauge the tech stack at a glance.
  • Status: Represents the current state of metrics collection for each repository. The status values indicate the operational state of the metrics and are influenced by user actions, as follows:
    • Enabled: Metrics are actively running and being collected for the repository.
    • Disabled: Metrics have been turned off and are not being collected.
    • Restricted: Real-time metrics collection is limited because the webhook for this repository cannot be set up due to the Git provider user lacking repository admin permissions. Nonetheless, new commits will be processed every 24 hours, ensuring periodic updates are captured despite the webhook restriction.
    • Invalid: The user attempted to enable metrics, but it failed due to insufficient permissions or an issue setting up the necessary webhook.
    • NULL / Empty: This is the default state for newly fetched repositories or existing repositories when this feature is first deployed, indicating that no metrics have been enabled yet.
  • Progress: Displays the status of data processing fetched from the repository. Once ready, the bar turns green, indicating the number of commits in each repository.
  • Last Commit: Displays the timestamp of the last commit processed from this repository, giving you visibility into the most recent activity.
  • Ignored Files: You have the opportunity to exclude specific files or directories from the assessment, including libraries and other non-original code. This allows you to focus the analysis on the code you’ve written, ensuring that external libraries or irrelevant files are not included.

​
Enable metrics

Enabling Metrics on the repositories page is one of the major features of our tool. You will not be able to see valuable insights on the dashboards until you enable your metrics. When you Enable Metrics, our algorithm calculates data from your connected Git providers.

You can choose to Enable Metrics for a particular repository by selecting it and then clicking Enable Metrics on the right side of the table.

Alternatively, to enable metrics for several or all repositories, you can select them using the checkboxes on the left side. This will activate the Enable Metrics button, allowing you to perform a bulk run for your selected repositories.

Our tool integrates with Git providers to synchronize data and track repository changes.

We use webhooks for efficient, real-time updates. As a fallback, we employ a polling mechanism to fetch data at regular intervals. Admin access to the GitHub repository is required to configure webhooks. Once configured, our tool will receive and process updates in real-time whenever a relevant event occurs.

If webhook setup is not possible, our tool defaults to a polling method:

  • Frequency: Data is polled every 24 hours.
  • Scope: All repositories linked to the account are checked for updates.

In the Actions menu, you can also specify files that you want our tool to ignore. You can exclude specific files or directories from the assessment, including libraries and other non-original code. This allows you to focus the analysis on the code written, ensuring that external libraries or irrelevant files are not included. Additionally, you can exclude any other files or folders that you do not want to analyze. This is done via the .gitignore file, helping to refine the data analysis to focus on what matters most.

We understand that the data in your repositories may update, and you may connect additional repositories and Git providers.

To update the list of repositories, click the Re-fetch Repositories button. We recommend doing this whenever a new Git provider is connected or if you have trouble seeing the full list of repositories.

Contact us at support@p10y.com.

Here, you will find comprehensive information about all the repositories that have been successfully fetched after connecting your Git providers.

​
Repository Information

After establishing a connection with your Git providers, our tool collects essential data from your repositories. Below are the key pieces of information displayed for each repository:

  • Repository Name: The name of the fetched repository.
  • Project: The name of the project that this repository is part of.
  • Branch: The branch from which the data is being fetched, ensuring you are working with the latest changes.
  • Technology: The primary technology or programming language used in the repository, allowing you to gauge the tech stack at a glance.
  • Status: Represents the current state of metrics collection for each repository. The status values indicate the operational state of the metrics and are influenced by user actions, as follows:
    • Enabled: Metrics are actively running and being collected for the repository.
    • Disabled: Metrics have been turned off and are not being collected.
    • Restricted: Real-time metrics collection is limited because the webhook for this repository cannot be set up due to the Git provider user lacking repository admin permissions. Nonetheless, new commits will be processed every 24 hours, ensuring periodic updates are captured despite the webhook restriction.
    • Invalid: The user attempted to enable metrics, but it failed due to insufficient permissions or an issue setting up the necessary webhook.
    • NULL / Empty: This is the default state for newly fetched repositories or existing repositories when this feature is first deployed, indicating that no metrics have been enabled yet.
  • Progress: Displays the status of data processing fetched from the repository. Once ready, the bar turns green, indicating the number of commits in each repository.
  • Last Commit: Displays the timestamp of the last commit processed from this repository, giving you visibility into the most recent activity.
  • Ignored Files: You have the opportunity to exclude specific files or directories from the assessment, including libraries and other non-original code. This allows you to focus the analysis on the code you’ve written, ensuring that external libraries or irrelevant files are not included.

​
Enable metrics

Enabling Metrics on the repositories page is one of the major features of our tool. You will not be able to see valuable insights on the dashboards until you enable your metrics. When you Enable Metrics, our algorithm calculates data from your connected Git providers.

You can choose to Enable Metrics for a particular repository by selecting it and then clicking Enable Metrics on the right side of the table.

Alternatively, to enable metrics for several or all repositories, you can select them using the checkboxes on the left side. This will activate the Enable Metrics button, allowing you to perform a bulk run for your selected repositories.

Our tool integrates with Git providers to synchronize data and track repository changes.

We use webhooks for efficient, real-time updates. As a fallback, we employ a polling mechanism to fetch data at regular intervals. Admin access to the GitHub repository is required to configure webhooks. Once configured, our tool will receive and process updates in real-time whenever a relevant event occurs.

If webhook setup is not possible, our tool defaults to a polling method:

  • Frequency: Data is polled every 24 hours.
  • Scope: All repositories linked to the account are checked for updates.

In the Actions menu, you can also specify files that you want our tool to ignore. You can exclude specific files or directories from the assessment, including libraries and other non-original code. This allows you to focus the analysis on the code written, ensuring that external libraries or irrelevant files are not included. Additionally, you can exclude any other files or folders that you do not want to analyze. This is done via the .gitignore file, helping to refine the data analysis to focus on what matters most.

We understand that the data in your repositories may update, and you may connect additional repositories and Git providers.

To update the list of repositories, click the Re-fetch Repositories button. We recommend doing this whenever a new Git provider is connected or if you have trouble seeing the full list of repositories.

Contact us at support@p10y.com.