I am having a pipeline as follows:
...
pipelines:
default:
- parallel:
- step: name: 'Build and Test'
caches: - node
script:
- npm install
- npm test
...
pull-requests:
'**': # All
- parallel:
- step:
If I have a pull request open, I would like to ignore the default and keep only the check of the PR. Is it feasible?
Hello,
I assume that the use case you are referring to is an open pull request from e.g.
feature-branch -> master, and when new commits are pushed to feature-branch then run only the PR build and skip the default for feature-branch?
If so, then you can do the following: let's say you want to push 3 commits to feature-branch. In the commit message of the last commit, include
[skip ci]
so the commit message might look like
Creating files X and Y [skip ci]
This way, when you push, the default build won't run on the latest commit of feature-branch, but the PR build will still run.
Please feel free to let me know if this works for you and if you have any questions.
Kind regards,
Theodora
That is really helpful hint to add to the commit message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If i use [skip ci] in my commit message ,default build won't run on the latest commit of feature-branch, but the PR build also not running.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, the `[skip ci]` skips the CI altogether
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, also adding skip ci is somehow cumbersome
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.