<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=22220) </details> <!--IssueSummary end--> ### Description During a release rush the CI is quite full, and one may want to commit and postpone the CI run, but this can be done currenlty only pushing a new commit or rewording the last one. Sometime the `[ci skip]` annotation is viral enough to skip a pipeline in some protected branch after a merge, and in that case the burden is high, because one is forced to create a new MR with some minimal change, wait for the CI to complete, merge, and finally wait for the real CI run on the protected branch. ### Proposal Add an option to _Retry_ e skipped pipeline ### Links / references Related issues: - gitlab-ce#41122 - gitlab-ce#41535 - gitlab-ce#35192