Read-only projects
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com
A project is placed in a read-only state when it exceeds the allocated storage limit on the:
- Free tier, when any project in the namespace is over the free limit.
- Premium and Ultimate tiers, when any project in the namespace is over the fixed project limit.
When a project is read-only due to storage limits, you can't push or add large files (LFS) to the project's repository. A banner at the top of the project or namespace page indicates the read-only status.
Read-only namespaces
- Tier: Free
On the Free tier, a namespace is placed in a read-only state when it exceeds the free user limit, when the namespace visibility is private.
To remove the read-only state of a namespace and its projects, you can:
- Reduce the number of members in your namespace.
- Start a free trial, which includes an unlimited number of members.
- Purchase a paid tier.
Restricted actions
| Feature | Action restricted |
|---|---|
| Container registry | Create, edit, and delete cleanup policies Push an image to the container registry |
| Merge Requests | Create and update an MR |
| Package registry | Publish a package |
| Repositories | Add tags Create new branches Create and update commit status Push and force push to non-protected branches Push and force push to protected branches Upload files Create merge requests |
| CI/CD | Create, edit, admin, and run pipelines Create, edit, admin, and run builds Create and edit admin environments Create and edit admin deployments Create and edit admin clusters Create and edit admin releases |
| Namespaces | For exceeded free user limits: Invite new users |
When you try to execute a restricted action in a read-only namespace, you might get a 404 error.