Skip to content

WebIDE Default Commit options

Problem to solve

  • The WebIDE default commit option for a new change in the WebIDE of "Commit to Master" makes it easy for maintainers to accidentally push changes to master when the typical workflow would be to "Create a new branch and merge request"

Further details

Default_Commit

Proposal

All participants in https://gitlab.com/gitlab-org/ux-research/issues/220 confirmed that having Create a new branch selected would fit the preferred and usual workflow for the majority of cases. It is also easier to resolve the situation if you selected Create a new branch even though you actually wanted to commit directly to master, than the other way around. The new default option should thus be Create a new branch with Start a new merge request selected.

Commit to… Create a new branch Start a new MR Screenshot
Default branch (no matter the existence of an MR), user has write access for the branch 🔘 image
Default branch (no matter the existence of an MR), user has NO write access for the branch disabled 🔘 image
Protected branch (no matter existence of an MR), user has NO write access for the branch disabled 🔘 image
Non-default branch (no MR) 🔘 image
Non-default branch (existing MR) 🔘 hidden image

Links / references

Edited by Marcel van Remmerden