Sebastian (Tiedtke) Huckleberry

> FYI, I will move the other two repos to the new org this week. Repos were moved, @krook @lukaszgryglicki: - https://github.com/runmedev/runme - https://github.com/runmedev/runmejs - https://github.com/runmedev/vscode-runme - https://github.com/runmedev/docs.runme.dev

@krook We are currently working through these. I'll let you know when they complete. > * [ ] Migrate your Slack channels (if any) to the [Kubernetes or CNCF Slack...

Any chance your mono-repo is public? Could you point me to it, @rawkode? Fwiw, you can use `runme --project ./subdir` or `runme --project .` to hard restrict it's discovery to...

There are ways to make the experience better. However, unless you use a `devcontainer` with all the prerequisites, Runme executing Shell can't know "how valid" the runtime environment is. It's...

Thanks for reporting this issue, @eshepelyuk. We will look into it and get back to you.

Hi @znd4! Thanks for filing this issue. Could you please share an example or some steps to reproduce the issue? That'd be really helpful to speed up the investigation and...

Thanks for the thorough description. We'll work reproducing the issue and see what's possible @znd4. Will keep you posted here.

I believe what @adambabik meant to say was that `scriptisto` should be supported via `interpreter` in [the cell config](https://docs.runme.dev/usage/shebang#configuring-shebang-custom-interpreter-in-vs-code). I haven't tried this myself yet, @seivan. As you know, the...

> The Run Cell button does not seem to load `.bashrc` after the recent update. Hi @forseti, the latest `.bashrc` should load once you hit `Reset Session` in the notebook...

I think the issue is that we're forking/seeding the ENV with the systems, which trickles down from the `code` process. This is something we could do differently. It's good to...