### Description After every push against some of my repositories I'm doing lately I've found myself following the same repetitive steps: 1. Opening gitlab.com 2. Browsing to the target project 3. Opening the "Pipelines" tab 4. Searching for the right pipeline that I just created This process is way time consuming than I'd like it to be ### Proposal After running `git push` in the command line, it would be very useful to have the pipeline link echo'ed on the terminal if it was created (i.e. if the CI was not disabled / skipped). I'm a huge user of ⌘+click to open the merge-request after pushing some changes, the exact same procedure will be perfect for the pipeline URL: ``` $ git push Counting objects: 3, done. Delta compression using up to 4 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 334 bytes | 0 bytes/s, done. Total 3 (delta 2), reused 0 (delta 0) remote: remote: To create a merge request for <branch>, visit: remote: https://gitlab.com/<user>/<project>/merge_requests/new?merge_request%5Bsource_branch%5D=<branch> remote: remote: To see the pipeline created for this commit visit: remote: https://gitlab.com/<user>/<project>/pipelines/<id> remote: To gitlab.com:<user>/<project>.git 13a64ab..212adb3 <branch> -> <branch> ``` If this is too verbose, I'd consider a shorter version of the `remote` output to include both links or just the one to the pipeline's, since I usually check first if the tests were all green. In this sense, a button to create a MR could be located on the pipeline result page on success (where the "Retry" button is located in failed pipelines).