GitLab pivots on decision to wipe dormant projects

GitLab pivots on decision to wipe dormant projects
Ryan is a senior editor at TechForge Media with over a decade of experience covering the latest technology and interviewing leading industry figures. He can often be sighted at tech conferences with a strong coffee in one hand and a laptop in the other. If it's geeky, he’s probably into it. Find him on Twitter (@Gadget_Ry) or Mastodon (

GitLab appears to have pivoted on a decision to automatically wipe dormant projects.

On Thursday, The Register reported that GitLab planned to delete projects that have been inactive for a year and are owned by free users. The policy was due to come into effect in late September.

GitLab is said to have estimated the policy would save it up to $1 million a year. However, following the report, GitLab’s technically unannounced policy received significant backlash:

The company didn’t officially announce (or refute) the initially reported policy but today announced a variation:

The new policy strikes a fairer compromise—helping GitLab’s long-term financial viability while ensuring projects aren’t completely erased.

However, there’s still a question about how GitLab will define an inactive project.

Sid Sijbrandij, CEO and co-founder of GitLab, said that “probably all write operations would keep a project active, creating an issue, a merge request, pushing changes to a branch, etc. We might also keep it active as long as people are doing read operations such as cloning, forking, etc.”

Following Microsoft’s acquisition of GitHub, many developers switched to GitLab over concerns about the former’s direction under its new stewardship. GitLab isn’t exactly wooing over developers with such policies.

(Photo by Jim Wilson on Unsplash)

Looking to revamp your digital transformation strategy? Learn more about Digital Transformation Week taking place in Amsterdam, California, and London, and discover key strategies for making your digital efforts a success.

Tags: , , , , ,

View Comments
Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *