Improve exposure of mirroring errors
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Right now, we expose mirroring errors in a pop-up in Settings > Repository > Mirroring repositories. This is helpful for troubleshooting purposes and can allow a user to troubleshoot the issue on their own before contacting support.
However, not all errors are helpful or repeat more often than others when the mirror is retried again. (Please note the path to the branch was redacted in the below image)
In the above image, only the pre-receive hook failed error is shown, which is arguably less descriptive and helpful than the original error that caused the failure. Since we're not displaying anything historically, it requires logs to actually determine the reason for failure. Since we're only notifying users on hard failures, it might be useful to either provide some historical context in the user interface, or somehow filter out repetitive errors to only display the most relevant errors. Knowing when a mirror first fails seems ultimately helpful in figuring out mirroring problems.