Chris Patterson

Steps are run in their own process space and its own process memory, but, they are all run under the same user context and as a user you can read...

No we shouldn't move a community driven action into this namespace. We should limit it to only actions supported by GitHub employees directly. This action should be deprecated and removed...

I have no fundamental issue with having the setup tasks handle more environment configuration which can include downloading a runtime. One of the issues we have seen in the past...

@haacked But shouldn't your compile output still be relative to $GITHUB_WORKSPACE?

Yes.

I would say never rely on specific paths as they could change you should use the variables we provide to locate the root of your repository.

@StefanScherer a quick how-to can be found at https://docs.microsoft.com/en-us/vsts/build-release/actions/build-yaml?view=vsts. Essentially you turn on a preview feature and then create a new definition that points at the YAML file instead of...

The goal of this project is to provide a functional model for our customers to scale their own self-hosted infrastructure that fits their needs, not to provide a self-hosted model...

I would prefer to call it `pre` and just define that it runs `pre` on the machine. So no services would be configured etc. This would go along well with...

After thinking about this a bit more I think a better option would be to introduce a new `init` section in the YAML. This would be a set of steps...