Affichage des mesures des GitHub Actions

Vous pouvez afficher les mesures pour superviser où votre organisation ou vos référentiels utilisent GitHub Actions et comment elles fonctionnent.

Qui peut utiliser cette fonctionnalité ?

Organization owners and users with the "View organization Actions metrics" permission can view organization-level metrics.

Users with the base repository role can view repository-level metrics.

Dans cet article

Viewing GitHub Actions metrics for your organization

Remarque

There may be a discrepancy between the Workflows tab's job count and the Jobs tab's count due to differences in how unique jobs are identified. This does not affect the total minutes calculated.

  1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Click the name of your organization.

  3. Under your organization name, click Insights.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a graph icon and "Insights," is outlined in dark orange.

  4. In the "Insights" navigation menu, click Actions Usage Metrics or click Actions Performance Metrics.

  5. Optionally, to select a time period to view usage metrics for, choose an option from the Period drop down menu at the top right of the page. For more information, see Viewing GitHub Actions metrics.

  6. Click on the tab that contains the metrics you would like to view. For more information, see About GitHub Actions metrics.

  7. Optionally, to filter the data displayed in a tab, create a filter.

    1. Click on the Filter button.
    2. Click Add a filter.
    3. Choose a metric you would like to filter results by.
    4. Depending on the metric you chose, fill out information in the "Qualifier," "Operator," and "Value" columns.
    5. Optionally, click Add a filter to add another filter.
    6. Click Apply.

  8. Optionally, to download usage metrics to a CSV file, click .

Viewing GitHub Actions metrics for your repository

Remarque

There may be a discrepancy between the Workflows tab's job count and the Jobs tab's count due to differences in how unique jobs are identified. This does not affect the total minutes calculated.

  1. On GitHub, navigate to the main page of the repository.
  2. Under your repository name, click the Insights tab.
  3. In the "Insights" navigation menu, click Actions Usage Metrics or click Actions Performance Metrics.
  4. Optionally, to select a time period to view usage metrics for, choose an option from the Period drop down menu at the top right of the page. For more information, see Viewing GitHub Actions metrics.
  5. Click on the tab that contains the metrics you would like to view. For more information, see About GitHub Actions metrics.
  6. Optionally, to filter the data displayed in a tab, create a filter.
    1. Click on the Filter button.
    2. Click Add a filter.
    3. Choose a metric you would like to filter results by.
    4. Depending on the metric you chose, fill out information in the "Qualifier," "Operator," and "Value" columns.
    5. Optionally, click Add a filter to add another filter.
    6. Click Apply.
  7. Optionally, to download usage metrics to a CSV file, click .

Understanding GitHub Actions metrics aggregation

The time period selection feature allows you to view GitHub Actions metrics over predefined periods, as detailed in the following table. These metrics include skipped runs and those that use zero minutes. Data is presented using Coordinated Universal Time (UTC) days.

PeriodDescription
Current week (Mon-Sun)Data from Monday through the current day when the page is viewed.
Current monthData from the first of the month to the current day when the page is viewed.
Last monthData from the first day to the last day of the previous month.
Last 30 daysData from the last 30 days to when the page is viewed.
Last 90 daysData from the last 90 days to when the page is viewed.
Last yearData aggregated for the last 12 months.
CustomData from a custom date range. The range can be up to 100 days including the start and end dates and go back as far as one year.