Frontend: Disable the "Commit" and "Reset" buttons in the pipeline editor when no changes have been made
Release notes
Problem
Clicking on the "Commit" button when no changes were made to the config in the pipeline editor causes an empty commit and a running pipeline. Users can easily create multiple empty commits without realizing it since no confirmation is given for that action.
Expected behavior is that you shouldn't be able to make a commit if no changes were made to the configuration.
Research
Dovetail insight: Clicking on the "Commit" button when no changes were made unexpectedly causes an empty commit and a running pipeline.
Proposal
- Disable the "Commit" and "Reset" buttons in the pipeline editor commit form unless there's changes to the file.
 |
Intended users
Metrics
N/A
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.