This saves me a lot of time as a maintainer in some cases where otherwise I'd have to add the fork as a remote and then check it out locally.
Hoping that they'll add support for terminals as well at some point though I suspect maybe that'll forever be reserved for Codespaces.
1. Collaborative diagramming: https://twitter.com/hediet_dev/status/1425844785240236032
2. Lightweight notebook environment: https://twitter.com/DynamicWebPaige/status/14255023797770199...
3. Interactive walkthroughs: https://twitter.com/LostInTangent/status/1425901618780729345
I wonder with cloud setups if I'd ever be able to provision the environment how I want it setup? I want vim with syntastic and other bindings setup along with all my dot files.... I wonder how well that would work? Or will we all be forced into a kind of vanilla IDE setup and discourage any custom setups?
I do use VS Code's Settings Sync with my GitHub Account. I was surprised it wasn't on by default, but the menu steps to turn it on on the GitHub Dev site were very quick (didn't have to relogin, it did know which account I was already logged in under on the main GitHub site). It synced quickly with my Settings. It even pulled in some of my extensions, the most noticeable one being a custom color theme. Other than the obvious limitation to extensions that support "Virtual Workspaces", I'm not exactly sure why the subset of supported extensions is what it is. But it's neat that some of them show up. ("Virtual Workspaces" has been an interesting project to follow in VS Code's release notes and lets you do something similar to GitHub.Dev in your locally installed VS Code as well: open a remote GitHub repo you've never cloned/downloaded.)
(I have a Vim emulation extension to VSCode in my Settings Sync, but currently disabled for reasons in that I haven't used it in a while. It shows up as supported in the Extensions list on GitHub.Dev, which is interesting. Might try reenabling it and seeing how it works these days.)
After turning on Settings Sync once in GitHub.Dev it seems to remember it on subsequent visits (even from different repositories). Pretty neat.
It looks like GitHub.Dev only supports VS Code. If you want to provision an environment how you want it setup you could use Codespaces the next step up "big brother" tool to this GitHub.Dev site. (That gives you the ability to specify a full Docker container the Codespace runs in, including things like port forwarding SSH to allow working with vim, which GitHub mentioned doing in their recent Engineering blog about moving to Codespaces.)
What's the difference between the two? Github.dev redirects me to Codespaces.
(I work at GitHub)
FWIW, I had to disable Privacy Badger on github.dev, or it would not work. Complaining about not being able to resolve resources.
It's mentioned here https://github.com/features/codespaces
Codespaces, github.dev and github1s also kinda help with this although with a focus on helping on-boarding new team members. But IMO, in future, this could have features like export Dockerfile or any other format github desires.
It makes nix more relevant.