Antti
Antti
Your workflow's ```runs-on``` specifies the container image as ```ubuntu-18.04```, which doesn't have ```less``` installed by default. Replicating using that image: ``` # run ubuntu-18.04 as container > docker run -it...
Going by the main README section on default runners being [incomplete by design](https://github.com/nektos/act), it instructs to: > In case of any problems [please create issue](https://github.com/nektos/act/issues/new/choose) in respective repository (issues with...
Try running your flow again, this is likely temporary / github issue
What does the roadmap look like for this item, seems like it was removed from the plan for 1.3? Not having this makes 'this implementation supports GRPCRoutes' type proclamations misleading,...
Fully agree, would have a need for this use case as well. 'Standard' patches (e.g. ingress annotations adding protection/authentication/options) can add a lot of boilerplate that's unnecessary and could be...
Sorted out DCO - apologies.
Apologies for the direct tag @jamengual but would you mind triggering the CI/CD workflows when you have a sec?
Appreciate the concern. I had a quick look but not sure if there is a straightforward way for us to separate a 'summary' from other information that could leak info?...
Hi @jamengual , following up for feedback here. Happy to look at some additional security features if that would be useful.
This would be really great, kind of like a built-in `ngrok` equivalent to quickly share stuff. Thinking along those lines, could the command be, at its simplest, just: `telepresence share...