Inform users of pipeline starting after commit being pushed
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.
Problem to solve
Users currently often navigate to the pipeline list page after committing in order to find out if a pipeline has been created/started running.
Additionally, if the user used the web editor to push a commit, the pipeline status displayed in the info widget is often not seen, thus being too subtle.
Lastly, https://gitlab.com/gitlab-org/uxr_insights/issues/819 validates that sometimes this pipeline status may initially not be shown at all. This issue specifically is intended to be fixed by #30811 (closed)
Intended users
Further details
The problem of this issue has been validated with UX scorecard - Setting up GitLab-CI and can be reviewed with insight issue: https://gitlab.com/gitlab-org/uxr_insights/issues/818
Proposal
We show either a browser notification or a toast message after the user has pushed their commit.
We need to consider the following flows:
- User triggers a pipeline by pushing from the CLI
- User triggers a pipeline by using the web editor pushing to the same branch
- User triggers a pipeline by using the web editor pushing to a new branch
- User triggers a pipeline by using the web editor creating a new merge request
- User triggers a pipeline by using the Web IDE pushing to the same branch
- User triggers a pipeline by using the Web IDE pushing to a new branch
- User triggers a pipeline by using the Web IDE creating a new merge request