Evan Doyle

In case anyone else hits this, I added my user to the `docker` group as described here and this resolved the issue. https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

Hi @imsut ! Thanks for raising this. If I understand correctly, in addition to declaring dependencies like: ``` - path: module.a depends_on: - module.b - path: module.c depends_on: - module.b...

I think this makes sense. It seems like this would function mostly like guardrails for future changes to your modules. In other words it stops someone from simply running `tach...

@imsut In the case of multiple modules within the same package, the approach is typically to put the containing package in strict mode, and then re-export public members through the...

@imsut There is now a concept of `visibility` in Tach, which essentially functions as you described in one of your comments. If the `visibility` key doesn't match a given path,...

> hey @emdoyle I would love to work on this issue. since, its good first issue 👍 Sounds great! Feel free to put up a PR any time, and ask...

@shreyash2002 is this still something you'd like to work on? Otherwise I'll unassign so that someone else can pick it up.

@legendkartik45 That would be great, thanks! I might also recommend basing your branch on #208 to avoid significant merge conflicts when your changes are ready.

Hi @timgl ! Thanks for raising the issue, and trying out Tach. This usually means that there are no dependencies listed in your `tach.yml`, which could mean the source root...

Closing this due to inactivity. Taking it as feedback that `show` could use some love.