# 💬 Receive build failure info in a PR comment

**URL:** <https://discuss.bitrise.io/t/receive-build-failure-info-in-a-pr-comment/25547>\
**Category:** Website\
**Tags:** website, new-feature\
**Created:** [September 11, 2025, 7:30am UTC](https://discuss.bitrise.io/t/receive-build-failure-info-in-a-pr-comment/25547 "2025-09-11T07:30:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaushal.bitrise](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/kaushal.bitrise/32/5305_2.png) [@kaushal.bitrise](https://discuss.bitrise.io/u/kaushal.bitrise)\
**Post date:** [September 11, 2025, 7:30am UTC](https://discuss.bitrise.io/t/receive-build-failure-info-in-a-pr-comment/25547/1 "2025-09-11T07:30:14Z")

</div>

## What it does

Bitrise can now post build failure information directly in your pull request comments. This would reduce the need to open Bitrise while working on a new PR.

 ![example comment](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/7/7e836442d8b075c6c3f4372e901ed3979feccfc4.png)

## 🧩 The problem this solves

You’re reviewing code or waiting for CI feedback, a build fails, and now you have to:

- Leave your PR review context
- Navigate to Bitrise dashboard
- Dig through build logs to find the actual error
- Switch back to your PR to continue work

For some of us, this context switching slows down development and makes it harder to address build issues during code review quickly.

## 👉 How it works

 ![Opting into receiving comments](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/2/2def13afbd1338ab37b81ae0a68cf7c9dd4abe46.png)

The feature posts comments using either your service credential user account (OAuth) or the Bitrise GitHub App.

Comments contain concise error snippets plus links back to full logs on Bitrise.

> **💡 Pro tip** : Uncheck “build summary” to only get comments on failed builds, reducing noise from successful builds.

Read more about it [here](https://docs.bitrise.io/en/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/reporting-build-problems-in-pr-comments.html).

## When to use it

**Enable for projects where you want faster feedback loops:**

- Teams doing frequent PR-based development
- Projects with complex build processes that often fail
- When you want build context without leaving GitHub/GitLab/Bitbucket

## 📃 Docs

Read more about how to do this it 👉 [here](https://docs.bitrise.io/en/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/reporting-build-problems-in-pr-comments.html) 👈

---

<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 10, 2025, 7:30am UTC](https://discuss.bitrise.io/t/receive-build-failure-info-in-a-pr-comment/25547/2 "2025-11-10T07:30:37Z")

</div>

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