Better tools. Better news.
Thursday, September 3, 2026 · UTC
221 of 1222 in this edition
tech

GitHub Announces General Availability of Enterprise Live Migrations

GitHub's Enterprise Live Migrations tool is now generally available for near-zero-downtime server-to-cloud moves.

TruthFoundry News Desk
Share on X
Stands on 7 placed sources from 2 publishers.
Enterprise Live Migrations enable near-zero-downtime moves from GitHub Enterprise Server (GHES) to GitHub Enterprise Cloud with Data Residency (GHEC DR). [1] GitHub announced on September 3, 2026, that Enterprise Live Migrations (ELM) is now generally available for organizations. [2] GitHub stated that the cutover process for Enterprise Live Migrations takes just minutes, allowing developers to continue working throughout the migration. [3] The tool is designed to handle even the largest and most active repositories, including monorepos with extensive Git histories. [4] ELM enables near-zero-downtime migrations by continuously syncing data, allowing developers to keep working while the cutover only requires time to drain remaining in-flight changes. [5] The tool is purpose-built to handle massive monorepos with deep git history, large volumes of issues and pull requests, and constant activity around the clock. [6] Users can manage the ELM lifecycle through the gh elm CLI extension, which supports creating, monitoring, and initiating cutover via the GHES REST API. [7]
What this stands on
  1. Enterprise Live Migrations enable near-zero-downtime moves from GitHub Enterprise Server (GHES) to GitHub Enterprise Cloud with Data Residency (GHEC DR). · Blockchain.News
  2. GitHub announced on September 3, 2026, that Enterprise Live Migrations (ELM) is now generally available for organizations. · Blockchain.News
  3. GitHub stated that the cutover process for Enterprise Live Migrations takes just minutes, allowing developers to continue working throughout the migration. · Blockchain.News
  4. The tool is designed to handle even the largest and most active repositories, including monorepos with extensive Git histories. · Blockchain.News
  5. ELM enables near-zero-downtime migrations by continuously syncing data, allowing developers to keep working while the cutover only requires time to drain remaining in-flight changes. · The GitHub Blog
  6. The tool is purpose-built to handle massive monorepos with deep git history, large volumes of issues and pull requests, and constant activity around the clock. · The GitHub Blog
  7. Users can manage the ELM lifecycle through the gh elm CLI extension, which supports creating, monitoring, and initiating cutover via the GHES REST API. · The GitHub Blog
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:20Z.
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)2b1174856bb8a41a157a71e96aaa85a140f991d405e9022ddf0963e417630c22
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 editionKalpana Iyer Criticizes Showbiz 'Ghosting' of Actors