Admins can set no expiration (default), expiration at the next billing cycle, or a specific date; on that date GitHub removes the budget and the user falls back to the next applicable budget, with expires_at available in the Budgets REST API.

Temporary budget overrides expire automatically instead of silently becoming permanent, removing manual cleanup work at enterprise scale.

GitHub Now Lets You Set an Expiration Date for Individual User Budgets

Q: What shipped?

GitHub made expiration dates for individual user budgets generally available on September 1, 2026.

What shipped

GitHub has made expiration dates for individual user budgets generally available, announced September 1, 2026.

What changed

When creating or editing an individual user budget you can now choose: no expiration (the default), expiration at the start of the next billing cycle, or a specific date — changeable or clearable any time. On the expiration date GitHub removes the budget and the user falls back to the next budget that applies to them (their cost-center per-user budget or the universal budget). The Budgets REST API exposes the field as expires_at. Previously, temporary overrides had to be removed by hand at enterprise scale.

Why a builder cares

Temporary spend overrides can no longer silently become permanent — the cleanup is automatic, eliminating recurring billing hygiene work for org admins.

What shipped

What changed

Why a builder cares

Related reading