# Github Branch Protection: All Workflows need to succeed

**URL:** <https://discuss.bitrise.io/t/github-branch-protection-all-workflows-need-to-succeed/18119>\
**Category:** Question & Answer\
**Created:** [September 28, 2021, 8:40am UTC](https://discuss.bitrise.io/t/github-branch-protection-all-workflows-need-to-succeed/18119 "2021-09-28T08:40:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![armin-schnabel](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@armin-schnabel](https://discuss.bitrise.io/u/armin-schnabel)\
**Post date:** [September 28, 2021, 8:40am UTC](https://discuss.bitrise.io/t/github-branch-protection-all-workflows-need-to-succeed/18119/1 "2021-09-28T08:40:17Z")

</div>

Situation:

- we don’t have parallel builds
- we’re use multiple Bitrise workflows to test all our Android modules via `Virtual Device Testing`
- the next workflow is triggered at the end of the previous with `Bitrise Start Build`
- “Wait for Builds” is set to `false` as this would require parallel builds

Problem:

- when Github triggers our initial workflow `test1` and this succeeds the `Branch protection` allows to merge the PR
- when one of the other workflows fail this does not influence the `Branch protection`

Question:

- Can we “manually” control when Bitrise reports back to Github (success or not) without parallel builds?
- I.e. I would do this after the last workflow in the chain instead of currently after the first workflow

See screenshot:

- `test1` succeeds and starts `test2` which fails
- but Githubs still shows that all is good

![Screenshot from 2021-09-28 10-35-04](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/b/bf0b4f16b25663bc378210420ec3f42f73be2762.png)  
 ![Screenshot from 2021-09-28 10-35-20](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/5/54fcf7a0720fe8d1d58e9912637617cf456187ca.png)

---

<div class="post-metadata">

**Author:** ![cathy.harmon](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/cathy.harmon/32/2674_2.png) [@cathy.harmon](https://discuss.bitrise.io/u/cathy.harmon)\
**Post date:** [October 19, 2021, 2:03pm UTC](https://discuss.bitrise.io/t/github-branch-protection-all-workflows-need-to-succeed/18119/2 "2021-10-19T14:03:30Z")

</div>

Check out the [“Github Status”](https://app.bitrise.io/integrations/steps/github-status) step. It sounds like you may be able to use this to do what you would like.

One thing - if you are kicking off more then one build to do the tests, the last one finished will be the last one to set the status. So if you kick off 2 builds for testing, if the one that finishes first fails and sets the status, it will be overwritten by when the last build finishes - and the last build may be successful.

---

<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:** [November 18, 2021, 2:03pm UTC](https://discuss.bitrise.io/t/github-branch-protection-all-workflows-need-to-succeed/18119/3 "2021-11-18T14:03:57Z")

</div>

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