Temporary interaction limits get longer and wider reach

GitHub has expanded its temporary interaction limits with two notable changes: longer limit windows and a new user-wide setting that applies a single limit across all personal repositories.

Extended limit durations

Repository maintainers can now choose from six limit durations: 24 hours, three days, one week, one month, or six months. The six-month option provides a longer runway for projects that need sustained moderation, whether to manage bursts of attention, step away temporarily, or curb spam and abusive behavior.

Screenshot showing setting of timed interaction limit

One toggle for all personal repositories

For maintainers juggling multiple public repositories, enforcing limits individually can become tedious. A new user-level setting under “Interaction limits” in user settings applies the chosen limit to every public, user-owned repository at once. This is particularly useful for maintainers who need to pause activity across an entire open source portfolio quickly.

Screenshot showing setting user-wide interaction limits

API support

Both the REST and GraphQL APIs now expose the full range of interaction limit capabilities. The REST API documentation covers setting longer durations or applying limits user-wide. On the GraphQL side, you can query interaction limits and set or disable them for repositories, users, and organizations, matching the behavior available through REST.

For details on applying limits at each level, refer to the documentation for single repository limits, user-wide limits, and organization-wide limits.