# I have some problems with Push and Pull Request triggers

**URL:** https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868
**Category:** Tooling Issues
**Created:** [May 6, 2020, 4:08am UTC](https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868 "2020-05-06T04:08:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![luciano.lima](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/luciano.lima/32/2937_2.png) [@luciano.lima](https://discuss.bitrise.io/u/luciano.lima)
#### Post date: [May 6, 2020, 4:08am UTC](https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868/1 "2020-05-06T04:08:23Z")

</div>

I think it’s my fault and because this I decide to get help here.  
I have some workflows with Push and Pull Request triggers:

```auto
trigger_map:
- push_branch: release/*
  workflow: native-build
- push_branch: master
  workflow: versioning
- push_branch: "*"
  workflow: test
- pull_request_source_branch: hotfix/*
  pull_request_target_branch: master
  workflow: hotfix
- pull_request_source_branch: release/*
  pull_request_target_branch: master
  workflow: native-build

```

My case: I start a release branch, merge some PRs in this branch and in sprint end I create a release pull request. My attempt is: always I have a push to release branch or pull request from release branch to master, calls native-build workflow.  
But with this setup I have some loops in workflow calls when the Pull Request is merged on master from release branch. I don’t understand the reason for this and need some guidance from you guys here. I know that when I merge, it’s triggers a push too, but I don’t have any trigger for push on master.

---

<div class="post-metadata">

### Author: ![luciano.lima](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/luciano.lima/32/2937_2.png) [@luciano.lima](https://discuss.bitrise.io/u/luciano.lima)
#### Post date: [May 16, 2020, 3:32am UTC](https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868/2 "2020-05-16T03:32:14Z")

</div>

For what I can discover, PR trigger does not respect `[skip ci]` in commit message or description.  
This is right?!

---

<div class="post-metadata">

### Author: ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)
#### Post date: [June 2, 2020, 8:09am UTC](https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868/3 "2020-06-02T08:09:42Z")

</div>

Hi @luciano.lima!

This is completely correct, please see: [https://devcenter.bitrise.io/builds/triggering-builds/skipping-a-given-commit-or-pull-request/#skipping-a-pull-request](https://devcenter.bitrise.io/builds/triggering-builds/skipping-a-given-commit-or-pull-request/#skipping-a-pull-request)

In short, if you want to skip a pull request, you have to include the `skip ci` pattern in the pull request’s title or description, and not in the commit’s message.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)
#### Post date: [July 2, 2020, 8:09am UTC](https://discuss.bitrise.io/t/i-have-some-problems-with-push-and-pull-request-triggers/12868/4 "2020-07-02T08:09:44Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
