When viewing a build that reconfigures pipelines, it's hard to tell which pipelines were actually changed:

Quick suggestion: highlight it in yellow, like the get step? Or the opposite - dim steps which had no changes to apply? No strong preference!

This would likely involve emittin

JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.

http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Opencover allows hiding skipped modules by providing a `hideskipped parameter. Would be great to add this.
See https://github.com/OpenCover/opencover/wiki/Usage#console-application-usage for details.

What happened:

UI is loading all the step log data in memory and looping through the data to create a blob to make it downloadable. This does not work for large step log files where there are hundred thousands of log lines.

What you expected to happen:

1. UI should not do any custom logic and should defer to API for log download.
2. New API to download step logs with proper cachi

Github sends a notification if you are @mentioned in a commit message. This is unfortunate, because you'll get repeated notifications when the commit is rebased (or when you try several merges). Arguably, this is a bug in GitHub, but it seems like it's easier to fix this on bors' side, by escaping all @mentions