Lukas Berger

> Can you also clarify how I would pass in the GOOGLE_BUILDABLE environment variable? Here's an updated `cloudbuild.yaml`: ``` steps: - name: 'gcr.io/cloud-builders/gcloud' entrypoint: '/bin/bash' args: - '-c' - >...

Thank you for filing the issue. Pack does not provide access to the git credentials that you have stored locally, so private dependencies will be inaccessible by Go. Unfortunately we...

IIRC we added this check because functions would often fail at run time and it was difficult for customers to access the logs to determine the failure reason. [`.gcloudignore`](https://cloud.google.com/functions/docs/deploying/filesystem) is...

As a workaround, you can add `GOOGLE_RUNTIME=nodejs` to `project.toml`. Would you mind running `pack build` with the `-v` flag to see why buildpacks are opting out? As to running `detect`...

This sounds similar to https://github.com/GoogleCloudPlatform/buildpacks/issues/87. Does the `GOOGLE_BUILDABLE` environment variable help here?

`pack`, similarly to `docker` will only include the files in the current directory (or the directory specified by `--path`) in the build context. The project you link is structured in...

It's applicable to Go as well, so it's under the Common Options section: https://github.com/GoogleCloudPlatform/buildpacks#common-options. By the .NET section do mean the under "default entrypoint behavior"?