heroku / heroku/roadmap

Build logs should contain commit sha

Open
#333 0 comments 0 reactions 0 assignees View on GitHub
Proposed
Dominant language
No language data
Stars
225
Forks
19
PR merge metrics
No merged PRs in 30d

Description

### Required Terms

- [x] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [x] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)

### What service(s) is this request for?

Dashboard

### Tell us about what you're trying to solve. What challenges are you facing?

Please make it visible in the build log, which commit it belongs to.

When the build is successful and it deploys right after, it is usually easy to figure out which commit it belongs to. But if it fails, then there is no information.

When you have automated deploys from Github enabled, you can easily create a bunch of builds without knowing which belongs to which commit.

Having the commit sha in the build log, would make it easier to trace back where build problems come from.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.