Skip to content

Mark stale prs CI has a very low limit #140279

Description

@StanFromIreland

Feature or enhancement

The CI has a limit of 120, as can be seen in today's run.

Looking at the docs on rate limits, IIUC the action would fall under:

GitHub Apps authenticating with an installation access token ... on a GitHub Enterprise Cloud organization, the installation has a rate limit of 15,000 requests per hour.

There is also the option of adding a GITHUB_TOKEN to increase the limit to 15000.

Linked PRs

Activity

  1. added
    type-featureA feature request or enhancement
    infraCI, GitHub Actions, buildbots, Dependabot, etc.
    on Oct 18, 2025
  2. hugovk commented on Oct 18, 2025

    @hugovk
    Member

    GitHub Apps authenticating with an installation access token ... on a GitHub Enterprise Cloud organization, the installation has a rate limit of 15,000 requests per hour.

    Does actions/stale run as a GitHub app? (re: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-github-app-installations)

    Or is it running as a GitHub Actions workflow? (re: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#primary-rate-limit-for-github_token-in-github-actions)

    You can use the built-in GITHUB_TOKEN to authenticate requests in GitHub Actions workflows. See Use GITHUB_TOKEN for authentication in workflows.

    The rate limit for GITHUB_TOKEN is 1,000 requests per hour per repository. For requests to resources that belong to a GitHub Enterprise Cloud account, the limit is 15,000 requests per hour per repository.

    The actions/stale docs say of operations-per-run:

    These operations are made in a very short period of time — because the action is very fast to run — and can be numerous based on your project action configuration and the quantity of issues and pull requests within it.

    And:

    When debugging, you can set it to a much higher number like 1000 since there will be fewer operations made with the GitHub API.
    Only the actor and the batch of issues (100 per batch) will consume the operations.

    Would 5,000 requests use up our 1,000/hour quota very quickly and cause other workflows to stop running?

  3. hugovk commented on Oct 18, 2025

    @hugovk
    Member

    See also #113858 to fix a related problem, in that the stale cache gets deleted before it can be used again, and #139623 that should remove that problem.

  4. StanFromIreland commented on Oct 18, 2025

    @StanFromIreland
    MemberAuthor

    Reading GitHub's documentation it is not clear to me whether the uses: package is an installation or not. How about we increase to 800? Do the other workflows even use the API I wonder, per the actions/checkout docs Git is used, with a fallback to the API if that fails.

  5. added a commit that references this issue on Apr 6, 2026
  6. StanFromIreland commented on Apr 9, 2026

    @StanFromIreland
    MemberAuthor

    With the cache it's slowly but surely making progress, closing.

  7. added a commit that references this issue on Apr 25, 2026
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

    infraCI, GitHub Actions, buildbots, Dependabot, etc.type-featureA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions