Skip to content

Add interval to config file #12143

Description

@corani

Describe the feature or problem you’d like to solve

With the default interval of 10 seconds I regularly get secondary rate limit errors when using e.g. gh pr checks --watch. I can change the interval by providing a --interval 30 parameter, but having to provide that each time is annoying.

Proposed solution

Add an option to the config file to specify the default interval value.

Additional context

Activity

  1. github-actions commented on Nov 13, 2025

    @github-actions
    Contributor

    Thank you for your issue! We have categorized it as a feature request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.

    Unless you see the help wanted Contributions welcome label, we are not currently looking for external contributions for this feature.

    If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.

  2. babakks commented on Nov 13, 2025

    @babakks
    Member

    Hi @corani! 👋 I understand your use case, but note that config params meant to be cross-cutting/common tweaks among gh commands.

    I believe, in your case, it's better to use gh aliases. For example you can define pr-checks with this:

    gh alias set prc 'pr checks --watch --interval 30'

    And then use it as gh prc. Does this help with your use case?

  3. added
    more-info-neededMore info needed from user/contributor
    gh-prrelating to the gh pr command
    on Nov 13, 2025
  4. corani commented on Nov 14, 2025

    @corani
    Author

    As a workaround, yes (thanks for the suggestion!). But I think the interval is a cross-cutting concern that could apply to all commands that allow setting an interval, as I'd suspect they'd all be subjected to rate-limiting.

  5. babakks commented on Nov 14, 2025

    @babakks
    Member

    No worries! 🍻

    As for interval, it's not a common option within gh commands with only two instances. Also, it's more about polling practices, and user experience. Definitely it helps avoiding rate-limit issues, but that a fortunate byproduct.

  6. github-actions commented on Dec 15, 2025

    @github-actions
    Contributor

    This issue has been automatically marked as stale because it has not had any activity in the last 30 days,
    and it will be closed in 30 days if no further activity occurs.

    If you think this is a mistake, please comment on this issue to keep it open.

  7. github-actions commented on Jan 14, 2026

    @github-actions
    Contributor

    This issue has been automatically closed due to inactivity.

    If you think this is a mistake, please comment on this issue.

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

    enhancementa request to improve CLIgh-prrelating to the gh pr commandmore-info-neededMore info needed from user/contributorneeds-triageneeds to be reviewedstale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions