### Problem to solve We have our Jenkins pipeline reporting commit statuses into Gitlab - these show up as a Pipeline step. We have CD set up to automatically Since Pipeline's can be skipped I tried just posting to the `/projects/:id/statuses/:sha` API with `state=skipped` only to find it was not an accepted state. Another use case for Skipped state is for longer running CI jobs. If you push commit 1 and it is still in a queue and then you push a new commit 2, being able to mark commit 1 as skipped would be nice. ### Proposal ### What does success look like, and how can we measure that? The Commit build status API accepts a "skipped" state - https://docs.gitlab.com/ce/api/commits.html#post-the-build-status-to-a-commit. I think since Pipeline's already have a skipped state much of the rest of the UI and system already deals with the possibility of a commit in this state. (well a pipeline, but commit statuses appear as external pipelines already). I could be wrong about this though as I am not familiar with the internals of Gitlab