Version updated for https://github.com/hesreallyhim/github-api-usage-tracker to version v1.2.0. This action is used across all versions by 2 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action tracks and reports the number of GitHub API requests consumed during a workflow job, categorized by rate-limit buckets (e.g., core, GraphQL, search). It automates the process of monitoring API usage by capturing the rate-limit state at the start and end of a job, providing a clear summary of usage in the workflow UI.

Version updated for https://github.com/hesreallyhim/github-api-usage-tracker to version github-api-usage-tracker-v1.1.0. This action is used across all versions by 2 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action, “GitHub API Usage Tracker,” monitors and tracks the number of GitHub API requests consumed during a workflow job, categorized by rate-limit buckets (e.g., core, GraphQL, search). It automates the process by capturing API usage at the start and end of a job, providing a detailed summary of the total requests used, remaining limits, and breakdown by bucket.

Version updated for https://github.com/hesreallyhim/github-api-usage-tracker to version v1.0.2. This action is used across all versions by 1 repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action tracks the usage of GitHub API requests within a workflow job, categorized by rate-limit buckets such as core, GraphQL, and search. It automates the process of capturing API rate-limit states at the start and end of a job, providing detailed insights into API consumption and remaining limits.

Version updated for https://github.com/hesreallyhim/github-api-usage-tracker to version v1.0.0. This action is used across all versions by ? repositories. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action tracks and reports the GitHub API usage of a workflow job by capturing the API rate-limit state at the start and end of the job. It automates the process of monitoring how many API requests are consumed, categorized by rate-limit buckets (e.