-
Currently OneDev can not skip CI based on commit message pattern. However you may specify patterns of changed files applicable for a job:

For instance, you may specify below pattern to exclude all html files from triggering the job:
-**/*.html -
Name Previous Value Current Value Type
Discussion
Improvement
-
Previous Value Current Value How to "Skip" CI based on commit message?
Skip running job for branch update and pull request update trigger when commit message contains "[skip ci]" or "[ci skip]"
-
OneDev
changed state to 'Closed' 4 years ago
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 4 years ago
Previous Value Current Value Closed
Released
-
State changed as build #2749 is successful
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
Apologies if I'm completely missing this somewhere, but is there an option in OneDev to "skip" a CI run?
Use case: My CI/CD build is set to run on all branch pushes. My CI build actually commits code changes to the repository. When the CI runs, it actually triggers another run because the commit fires the CI again. I'd like my CI build to include a commit message like other CI/CD solutions to skip the run and ignore it.
Ref: