Our users have been using the batch details page a lot, and have found it a bit confusing to learn that the cause of a failure is a merge conflict. The details page appears confusing (with an empty list of statuses):
The developer has to know to navigate via the PR to look at the commit status (which shows
bors - Merge conflict)
Ideally, we'd like to show the
bors status message on this page as well, but currently this not persisted in the database. Given this implementation would require a schema change, we wanted to get your thoughts on this change.
More completely, the change would involve adding a new column to the
batches table, called
status_message. It would get updated inside
Batcher.send_status to track the status sent to Github.