Won't run merge check pipeline

[Joshua]

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?

```yml

definitions:

  steps:

    - step: &test-ci

         name: Run unit tests (linting - warnings allowed)

         script:

           - yarn install

           - yarn lint:ci

           - yarn test:ci

    - step: &test-merge

         name: Run unit tests (linting - warnings not allowed)

         script:

           - yarn install

           - yarn lint:clean

           - yarn test:ci

pipelines:

  pull-requests:

    main:

      - step: *test-merge

  branches:

    main:

      - step: *test-merge

    "**":

      - step: *test-ci
```

[Joshua · Accepted solution]

Sadly, this was answered here: https://stackoverflow.com/questions/55019205/how-to-run-pipeline-only-on-pull-request-to-master-branch

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

[Saxea _Flowie_]

@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]

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.)

[Joshua]

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). :(