Source Code design monitoring 2025

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Overview

This issue will keep a running list of pieces of UI to monitor, due to low-risk design decisions that were made. Keeping tabs on any user feedback that comes in regarding these pieces of UI will help GitLab maintain quality of user experience.

Issue	Context	Design question	UI area	Repro steps
#502483 (comment 2285881375)	In the former commit changes modal, we allowed users to commit to existing branch + create a new merge request for this change. In the new commit changes modal, we only allow users to create a new merge request when they create a new branch. The decision made was to keep the new commit changes modal as is, under the assumption that most people will not be pushing to the default branch.	Will users want to commit to the current branch + create a new merge request?	Commit changes modal	Access the commit changes modal by any of the following steps: Code > Repository > Select a file > Edit > Edit single file Code > Repository > Select a file > Delete Code > Repository > Select a file > Replace Code > Repository > New file Code > Repository > Upload file Code > Repository > New directory
#516868 (closed)	When a file is locked by a user, the "Unlock" button is disabled for all other users. We allow users click "Replace" and "Delete," even though the UI will return an error if the user tries to commit changes on the current branch.	Will users who do not have permission to change a locked file want to Replace/Delete the file on a different branch?	File blob page	Visit a locked file Click "Replace" or "Delete"