Design: Align the pipeline editor commit form to the standard commit form component
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
What this issue is about
GitLab editors offer different commit experiences. The single file editor and the pipeline editor commit forms lack some features like selecting a branch to commit to. The inconsistent commit experience creates unnecessary burden for the users to get used to several different UIs to make a commit.
Proposal
Align the commit form in the pipeline editor to the standard commit form design defined in #333753 (closed)
Usability improvements uncovered during research
Users would like to be able to:
- Easier use conventional commits if their team follows those commit practices
- Select a branch from a dropdown list
- Have the default commit message be adjusted based on the changes they made to their config (for example if you changed stages, say “update stages” or if you edited a job, say “update job”.
Edited by 🤖 GitLab Bot 🤖