Skip to content

srz-zumix/ci-skip

Repository files navigation

ci-skip

CI skip commit meesage

CI Status [ci skip] [skip ci] Other Custom
AppVeyor Build status ☑️ ☑️ [skip appveyor] doc
Azure Pipelines Build Status ☑️ ☑️ skip-checks: true, ***NO_CI***,
[skip KEYWORD] or [KEYWORD skip]
(KEYWORD: azurepipelines, azpipelines, azp)
workaround
Bitrise Build Status ☑️ ☑️
Buddy buddy pipeline --skip
Circle CI CircleCI ☑️ ☑️
Cirrus CI Cirrus Build Status ☑️ ☑️
Codefresh Codefresh build status doc1, doc2
Codeship Codeship Status for srz-zumix/ci-skip ☑️ ☑️ --skip-ci,--ci-skip
Drone Build Status ☑️ ☑️ ***no_ci*** code
GitHub Actions GitHub Actions Status ☑️ ☑️ [no ci], [skip actions], or [actions skip] workaround
JFrog Pipelines [skipRun]
Peakflow Peakflow Build Status ☑️ ☑️
Razorops Razorops Build Status
Scrutinizer Build Status ☑️ ☑️
Semaphore CI Build Status ☑️ ☑️
Semaphore CI 2.0 Semaphore 2.0 Build Status ☑️ ☑️
Travis CI Build Status ☑️ ☑️ [skip KEYWORD] or [KEYWORD skip]
(KEYWORD: ci, travis, travis ci, travis-ci, or travisci)

Only the head/last commit message is checked

  • Travis CI
    Travis CI is build with all commit, If you are only interested in building the most recent commit you can use Auto Cancellation.
    Commit of the skip comment is not queued, so the previous commit will not be auto canceled.
  • Other than
    If you push more than one commit, only the last ("head") commit's message will be checked for the skip ci pattern!

Whether the skip build remains in the history

CI YES/NO
AppVeyor NO
AzurePipelines NO
Bitrise NO
Buddy YES (Activity Log)
Circle CI YES (Status SKIPPED)
Cirrus CI YES (Status SKIPPED)
Codefresh YES (Status SUCCESS)
Codeship NO
Drone NO
GitHub Actions YES (Status SKIPPED)
JFrog Pipelines NO
Peakflow NO
Razorops -
Scrutinizer NO
Semaphore CI NO
Semaphore CI 2.0 NO
Travis CI NO

GitHub commit status

https://github.com/srz-zumix/ci-skip/commits/master

Repository for CI service specification survey