Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Won't run merge check pipeline

Joshua August 17, 2023

Below is a snapshot of my `bitbucket-pipelines.yml` file. I'm trying to run a gate prior merging into main.

However, this will not run. (My trunk is `main`, but I've also tried with `master`.) What gives?



    - step: &test-ci
         name: Run unit tests (linting - warnings allowed)
           - yarn install
           - yarn lint:ci
           - yarn test:ci
    - step: &test-merge
         name: Run unit tests (linting - warnings not allowed)
           - yarn install
           - yarn lint:clean
           - yarn test:ci
      - step: *test-merge
      - step: *test-merge
      - step: *test-ci

2 answers

1 accepted

1 vote
Answer accepted
Joshua August 17, 2023

Sadly, this was answered here:


Definitely, not the "gate" I was looking for to protect the main branch.

0 votes
Saxea _Flowie_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 17, 2023

@Joshua We're currently working on a feature that enables more granular triggering of pipelines in Flowie. If you're interested in giving it an early trial, please get in touch via the website.

That being said, I believe you might be able to achieve your goal without this feature. Have you considered running 'lint:clean' on pull requests and have a 'build passing' check? This would only allow a merge to 'master' when linting is clean, which is what you seem to be aiming for.

Joshua August 17, 2023

I'm needing more than just lint:clean. There are actually a number of tests that I need to run, including Cypress for integration testing. I'm definitely interested in your product, as it has other features that, unfortunately Bitbucket does not. (It's hard coming from more mature CI tools like Azure DevOps and Circle CI.)

Like Saxea _Flowie_ likes this
Joshua August 17, 2023

And, BTW, what you're suggesting, is what I'm trying to do. But, I want to have certain pipelines run depending on which branch you are attempting to merge into, not from the branch you are merging from (which, is apparently how Bitbucket is designed). :(

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events