Make pipeline output easier to understand when your pipeline fails on a handbook edit that should pass
Problem to solve
Sometimes a handbook edit you make cannot be deployed because your pipeline fails. In some cases, the pipeline fails due to someone else's change breaking master and not because of the change you made. It is a frustrating experience when this happens because, unless, you are quite technical, it can be difficult to understand why your change failed and what to do about it.
This MR is a great example.
Intended users
Non-technical users who make changes to the handbook.
Proposal
As a MVC, let's pull out important information at the end of the pipeline log in order to explain in layman's terms what's going on. At a minimum, the pipeline should indicate if it failed because of something you changed, or because or another reason.