Chris Patterson

For something like bazel I wonder if having a truly remote cache is actually a better option https://github.com/buchgr/bazel-remote. This is not something we are going to get around to implementing...

> A truly remote cache is an appealing option, but comes with a lot more > operational overhead for the user. Storing files is much easier than > running a...

The only recent changes we have made in the are of service containers was to stop overriding the workdir and adding the workspace volume mounts. It is possible that is...

Moving the repository outside of the workspace would break any actions that work on the contract that the repository is at that location. For self-hosted runners you can configure the...

@billhenn When configuring the runner you can put the runner binaries wherever on disk you want and then you can pass the `--work` parameter and give it a completely different...

@mikkelbd we now have an api for downloading artifactshttps://developer.github.com/v3/actions/artifacts/#download-an-artifact so you could likely accomplish your scenario now.

We don't currently have that parameter to the API but I will add it to our feedback list to consider for the future.

> The covered gem has access to the `travis_job_id` when running on Travis which is all Coveralls needs to hook up the jobs. I am not sure why coveralls needs...

If we were to implement this capability we would probably do it with an input as @wipe2238 suggests. Given the majority of cases don't need to deal with the complexity...

The new Actions Runner Scale Set has an option to use native Kubernetes apis instead of docker in docker for running container actions in a workflow https://github.com/actions/actions-runner-controller/releases/tag/gha-runner-scale-set-0.4.0. This should resolve...