Andrea Falzetti

> I was testing it and If I specify the namespace through the flag `-n`, we don't show the context information, but prior this change, we were displaying it >...

Thanks for contributing with your ideas, @rishitashaw! In Go, it's preferred to return errors instead of throwing exeptions, like panicking. Also, deprecation is a great way to let the users...

Hi @rishitashaw, apologies for the delay in getting back to you. Any code change must be submitted via a PR, it's hard to review from comments in issues as there...

Thanks for your interest in contributing to the Okteto CLI, @khareyash05. I am afraid that at the moment we are not onboarding new contributors to the project. We are focusing...

Re-opened for 3.0

At the moment the URL is mandatory, so I think the UI always prints the "Endpoints" label. We should make the label optional if the URL is present before removing...

@AnshulAngaria thanks for offering, this is a bit tricky because it requires an initial investigation to understand what approach to use and potentially do a refactor. It's also part of...

I can reproduce this behavior and I want to add extra info to explain what's happening. Regardless if the user adds the vanilla k8s context to the okteto config (via...

> Yep, for us embedding would be a valuable feature too, though I understand all the complications =\ Could you elaborate more on how you would benefit from having this...

We have now made some small progress towards this. During a Gitpod hackathon we've created [this branch](https://github.com/gitpod-io/gitpod/tree/hackathon/devcontainer). There's a lot of clean-up required. We commented out useful code during our...