Better tools. Better news.
Thursday, September 3, 2026 · UTC
248 of 1221 in this edition
ai

GitHub Adds Optional Expiration Dates to Individual User Budgets

GitHub has made expiration dates for individual user budgets generally available to simplify enterprise budget management.

TruthFoundry Desk
from the fact record
Share on X
Stands on 7 placed sources from 2 publishers.
GitHub has made the capability to set an optional expiration date on an individual user budget generally available. [1] GitHub rolled out a new feature on 2026-09-01 allowing administrators to set expiration dates on individual user budgets for Copilot Business and Enterprise plans. [2] Previously, administrators had to manually remove every temporary budget override by hand, which created recurring cleanup work at enterprise scale. [3] When an individual user budget expires, the user automatically falls back to the next applicable budget, such as their cost center per-user budget or their universal budget. [4] Administrators have three options when creating or editing a budget: no expiration, expiration at the start of the next billing cycle, or expiration on a specific date. [5] The feature adds an expires_at field to the Budgets REST API, and when an expiration date is reached, the individual budget is removed and the user transitions to the next applicable budget such as a cost center or organization-wide budget. [6] In July 2026, GitHub introduced features for tracking AI credit usage per billing cycle, and earlier that month added per-user states for multi-user budgets in the REST API. [7]
What this stands on
  1. GitHub has made the capability to set an optional expiration date on an individual user budget generally available. · The GitHub Blog
  2. GitHub rolled out a new feature on 2026-09-01 allowing administrators to set expiration dates on individual user budgets for Copilot Business and Enterprise plans. · Blockchain.News
  3. Previously, administrators had to manually remove every temporary budget override by hand, which created recurring cleanup work at enterprise scale. · The GitHub Blog
  4. When an individual user budget expires, the user automatically falls back to the next applicable budget, such as their cost center per-user budget or their universal budget. · The GitHub Blog
  5. Administrators have three options when creating or editing a budget: no expiration, expiration at the start of the next billing cycle, or expiration on a specific date. · Blockchain.News
  6. The feature adds an expires_at field to the Budgets REST API, and when an expiration date is reached, the individual budget is removed and the user transitions to the next applicable budget such as a cost center or organization-wide budget. · Blockchain.News
  7. In July 2026, GitHub introduced features for tracking AI credit usage per billing cycle, and earlier that month added per-user states for multi-user budgets in the REST API. · Blockchain.News
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 7 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-03T12:16Z.
The prompts, verbatim
System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)e314843dbee03a740126fd798a9181a8ce1f4b823b9b5f0b0a0c11538381bc24
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.

Up next in this editionChina's Solar Capacity Surpasses Coal for First Time