Paymahn Moghadasian

What's interesting is that the single commit in the list is correct and as expected. Is github complaining that the merge commit in `prod` is not present in `prod-promotion`?

We've seen subgraphs up to 1.9 million data sources. Not sure if that matters at all for how this should be handled.

``` ❮❮❮ kubectl exec --namespace default -it statefulset/atlantis -- /bin/bash atlantis-0:/$ terraform workspace list * default ``` It seems the default workspace does exist. The path printed in the error...

ah, removing ``` ATLANTIS_INCLUDE_GIT_UNTRACKED_FILES: true ``` seems to fix the issue, now my logs say ``` atlantis-0 atlantis {"level":"info","ts":"2024-08-06T20:47:20.823Z","caller":"events/working_dir.go:235","msg":"creating dir '/atlantis-data/repos/goldsky-io/goldsky-infra/1286/default'","json":{"repo":"goldsky-io/goldsky-infra","pull":"1286"}} ``` but there are other issues for me to...

I bumped the volume to 20gb and haven't had the issue since

It would be great if we could have a config option to choose between merge and rebase when merging the PR

Here's the service definition ``` graph-node: restart: always build: context: . dockerfile: graph-node.Dockerfile ports: - ports depends_on: - dependencies extra_hosts: - "host.docker.internal:host-gateway" environment: env-vars command: some-command volumes: - stuff ```...

``` ❮❮❮ docker context use orbstack orbstack Current context is now "orbstack" 3:44PM /Users/paymahn/code/goldsky/graph-tools/packages/e2e-tests paymahn/aaaaa-local-graph-node-debugging ⬆ ⬇ ✭ ✱ ❯❯❯ docker image inspect 716091368358.dkr.ecr.us-west-2.amazonaws.com/graph-node:v0.35.1.0 | jq '.[].Architecture' "arm64" ``` I'm...

Following up here, still have this issue.

Following up again @slinorb