# Pull request branches to include code coverage

**URL:** <https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318>\
**Category:** Suggest new features\
**Tags:** branches, coverage\
**Created:** [June 18, 2018, 4:00pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318 "2018-06-18T16:00:08Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![Thomas.Thorne](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/thomas.thorne/32/188_2.png) [@Thomas.Thorne](https://community.sonarsource.com/u/Thomas.Thorne)\
**Post date:** [November 8, 2018, 3:36pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/21 "2018-11-08T15:36:30Z")

</div>

Now that the request at [https://jira.sonarsource.com/browse/MMF-1118](https://jira.sonarsource.com/browse/MMF-1118) is marked as Fixed can you give an ETA on the release date or release number that will include it?

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 8, 2018, 3:57pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/22 "2018-11-08T15:57:45Z")

</div>

Hi,

This was delivered in 7.4.

> [@SonarQube 7.4 Released](https://community.sonarsource.com/t/sonarqube-7-4-released/3792):
>
> Hi all, :confetti\_ball:SonarSource is proud to announce the release of SonarQube 7.4 today!confetti_ball You can find the details of the most compelling new features in the [official announcement](https://www.sonarqube.org/sonarqube-7-4/). In addition, here are a few things you probably want to take note of: Coverage is now available on PRs and short-lived branches heart_eyesWe’ve added granular “create” permissions for Portfolios and Applications, and users with any create permission (including projects!) now have access to do…

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Thomas.Thorne](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/thomas.thorne/32/188_2.png) [@Thomas.Thorne](https://community.sonarsource.com/u/Thomas.Thorne)\
**Post date:** [November 8, 2018, 4:19pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/23 "2018-11-08T16:19:39Z")

</div>

Thank you. I shall as our DevOp or IT guys to try applying the update to our system so that we get the new feature! 😺

---

<div class="post-metadata">

**Author:** ![barfet](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/barfet/32/1292_2.png) [@barfet](https://community.sonarsource.com/u/barfet)\
**Post date:** [November 20, 2018, 12:05pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/24 "2018-11-20T12:05:36Z")

</div>

Hi Ann,

Great news! Maybe you know when it will be available in SonarCloud as well?

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 26, 2018, 8:21pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/25 "2018-11-26T20:21:00Z")

</div>

Hi @barfet,

This was available in Sonarcloud before it was available in SonarQube.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![barfet](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/barfet/32/1292_2.png) [@barfet](https://community.sonarsource.com/u/barfet)\
**Post date:** [November 27, 2018, 9:34am UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/26 "2018-11-27T09:34:44Z")

</div>

Hi @ganncamp,

Thank you for your reply.  
Maybe you could clarify this one.  
Currently we’re using SonarCloud with Azure DevOps and set it up for master and feature branches.  
On each PR we trigger build + SonarCloud check (approve from SC is required).  
But currently SC doesn’t count a test coverage metric in quality gate for short lived branches (PR) and you could merge a PR without passing a test coverage check.  
I thought that we’re talking about this metric and you add support for this kind of scenario (block PR, for example, if test coverage is less that 80% on new code). If we’re talking about the same staff, maybe you could suggest how we could set up it in SonarCloud? Because we don’t have such functionality i a moment.

Thanks!

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 27, 2018, 1:45pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/27 "2018-11-27T13:45:45Z")

</div>

Hi,

> [@barfet](#):
>
> But currently SC doesn’t count a test coverage metric in quality gate for short lived branches (PR) and you could merge a PR without passing a test coverage check.

Sorry to be pedantic, but reading your coverage report and applying a coverage criteria in a quality gate are two different things. 7.5 will add duplication calculation on PRs and SLBs, and hopefully 7.6 will [add “real” quality gates](https://jira.sonarsource.com/browse/MMF-1369).

And before you start to yell, please check the other threads in this community where everyone else has already yelled. Feel free to click hard when you ‘like’ those posts.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [February 11, 2020, 2:38pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/28 "2020-02-11T14:38:10Z")

</div>

Since the feature has been implemented, I’m closing this topic to release the votes back to the users to reapply on other topics.

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [February 11, 2020, 2:38pm UTC](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318/29 "2020-02-11T14:38:15Z")

</div>

Closed on February 11, 2020, 2:38pm UTC



[Previous page](https://community.sonarsource.com/t/pull-request-branches-to-include-code-coverage/318.md?page=1)
