Skip to content

ci: log GITHUB_TOKEN api-calls from the synced review callers #899

Closed as not planned

Description

@kyle-sexton

Problem

In melodic-software/claude-code-plugins, GITHUB_TOKEN's rate-limit header read 3,804 calls used for 2026-10-28 16:52-17:52Z. The per-job api-calls github-token=N notices accounted for only about 932 of them. The review callers this repository manages, pr-review-hosted.yml and pr-review-security-hosted.yml (listed under pull_request.paths in the consumer's pr-check-managed-files-hosted.yml), log no API-call counts, so their GITHUB_TOKEN spend can't be measured. Their resolve-model and kill-switch jobs and the reusable review workflows they call emit no api-calls notice. melodic-software/claude-code-plugins#10710 adds the notice to that repository's own jobs, but it can't edit these synced files.

Fix

Add the log-api-budget step, the same one the consumer's other jobs use (.github/actions/log-api-budget, which emits api-calls github-token=N), to every job in the two review callers and their reusable workflows that holds GITHUB_TOKEN. A job with no reading prints github-token=0 (claude-code-plugins#10710).

Acceptance

  • Each job in the synced review callers that runs on a runner and holds GITHUB_TOKEN emits one api-calls github-token=N notice.
  • No permission, secret or trigger changes.

Related

Activity

  1. kyle-sexton commented on Oct 30, 2026

    @kyle-sexton
    MemberAuthor

    Closing; the work belongs in ci-workflows. The synced caller has one job, pr-review (components/claude-lanes-hosted/claude-review.yml:74), and that job is only uses: melodic-software/ci-workflows/.github/workflows/pr-review.yml@main (:84). A uses: job can't hold a step, so the api-calls notice has to come from the reusable workflows, which is tracked in ci-workflows#905.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions