Group README: Web IDE fails first commit on empty gitlab-profile (18.4.2-ee)
Summary
When creating a Group README via “Add README” in a newly created group, the Web IDE fails to commit the initial README.md.
The project gitlab-profile is created, but the repository remains empty because the first commit is not performed.
Steps to reproduce
- Create a new group (no projects inside).
- From the group page, click Add README.
- Web IDE opens with
README.mdready to edit. - Enter any content and click Commit to main branch.
Expected behavior
- GitLab should create the hidden project
gitlab-profile. - Branch
mainshould be created automatically. - The first commit (
README.md) should succeed. - Afterwards, the Group profile page shows the README.
Actual behavior
-
The project
gitlab-profileis created, but remains empty (no branch). -
Web IDE shows:
Failed to commit changes. See the console for more information.
-
Server logs show:
POST /api/v4/projects/:id/repository/commits … status:404 (commit not found)
Additional details
- If the same commit is performed via API (
POST /projects/:id/repository/files/README.mdwithbranch=main), it works correctly. - If a project is created with “Initialize repository with a README”, the issue does not occur.
- The problem happens only in the Group README workflow with an empty
gitlab-profilerepo.
System information
- GitLab version:
18.4.2-ee (527e88bdddb) - GitLab Shell:
14.45.2 - Ruby:
3.2.8 - PostgreSQL:
16.10 Feature.get(:vscode_web_ide) => false- Installation: Omnibus, clean (no DB upgrade from previous version).
Workaround
Manually initializing README.md via API or CLI fixes the issue for that group.
After the first commit, Web IDE works fine.
Impact
- Prevents using Add README at Group level on a fresh installation.
- Confusing for users: the UI suggests it will work, but the commit always fails.
Edited by 🤖 GitLab Bot 🤖