I think there is a typo here:
https://github.com/concourse/concourse/blob/8e89cfce2b501b408b0cb841e6a2dab77b8ebe13/worker/workercmd/guardian.go#L59

The purpose of this RemoveAll call is to remove existing binaries that are older than it is bundled with. Surely guardian doesn't bundle old binaries :P

s/that/than/

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.

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

When running a DotNetCore command or tool via Cake, we can control the roll forward policy by setting an environment variable DOTNET_ROLL_FORWARD in the [tool's settings](https://github.com/cake-build/cake/blob/8bc15841e97944291946a89f335562244965247e/src/Cake.Common/Tools/DotNetCore/DotNet

Export headers are nice.

Currently, after every release, I manually update the NPM package. A workflow can be added to do this when a new release tag is created. Also the same can start publishing to GitHub Packages as well.

Ref:

• https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages