Skip to content
All tool news

Tool desk · Updated daily

Tool news·Netlify·

Netlify Adds Managed Git Repositories to Gitless Projects.

Netlify now creates managed Git repositories for projects without a Git host, supporting standard commits, diffs, pushes and merges.

CW

Create With tool desk

4 sources checked · 2 min read · 3 sections

ShareLinkedIn
Netlify Adds Managed Git Repositories to Gitless Projects

Netlify’s managed Git repositories now give every project arriving without a connected Git host its own source repository. The change adds the commits, diffs, pulls, pushes and merges needed when people and agents pass code changes back and forth.

Two years ago, 70% of new Netlify projects arrived without a Git host. Last month, that figure reached 93%, according to Netlify’s LinkedIn post. These projects enter through Netlify Drop, the API, its MCP server or an agent. Together, they account for millions of new projects each month.

New projects without a Git host
93%
last month
Previous share
70%
two years ago
Median workspace preparation
0.76 seconds
managed Netlify repository
GitHub-connected preparation
0.84 seconds
median

How Netlify’s Managed Git Repositories Work

Each project that arrives without a repository gets one managed by Netlify. It speaks standard Git, so builders can clone the repository and push it to another Git service.

The storage system uses S3 for durable data. Conditional writes prevent two servers from moving the same branch at the same time, handling the concurrency problem that appears when several processes update one repository.

Netlify also measured how long it takes to prepare the source workspace used for builds and agent runs. The median is 0.76 seconds for the managed repositories, compared with 0.84 seconds for projects connected to GitHub. Those figures cover source workspace preparation rather than the complete build.

Existing Git Connections Stay in Place

Projects connected to GitHub, GitLab, Bitbucket or Azure DevOps keep their current setup. Projects using Cursor Origin are unchanged too, following Netlify’s earlier addition of Cursor Origin repositories to continuous deployment.

That leaves builders with the same Git workflow for connected projects, while projects created through agents, the API, MCP or Netlify Drop gain a standard repository behind the scenes.

Netlify plans a second architecture post covering how it moved millions of existing projects onto the repository system.

Frequently asked questions

What are Netlify managed Git repositories?

They are standard Git repositories created for Netlify projects that arrive without a connected Git host. They support commits, diffs, pulls, pushes and merges, and can be cloned or pushed elsewhere.

Which Netlify plans include managed Git repositories?

The repositories are created for projects that arrive without a connected Git host. The announcement does not give plan or pricing details.

Do existing GitHub projects need to migrate?

No. Existing connections to GitHub, GitLab, Bitbucket, Azure DevOps and Cursor Origin continue to work as before.

Sources

4 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Latest tool news

What else changed this week.

All tool news
ChatGPTRoundup

GPT-6 Sol and Luna Roll Out Across ChatGPT

OpenAI shipped two new models this week, and three tools in our directory switched them on within hours of each other. GPT-6 Sol and GPT-6 Luna sit below Astra in OpenAI's line-up…

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.