├── .devcontainer └── devcontainer.json ├── .gitignore ├── README.md └── TODO.md /.devcontainer/devcontainer.json: -------------------------------------------------------------------------------- 1 | { 2 | "workspaceFolder": "azdo", 3 | "postCreateCommand": "git clone azdo" 4 | } 5 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | azdo 2 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Azure DevOps in Codespaces 2 | 3 | This repo template is built to help you get started developing your Azure DevOps-based codebases using Codespaces and Visual Studio. To get started, simply perform the following steps 👍 4 | 5 | **From GitHub.com:** 6 | 7 | 1. Click the `Use this template` button in order to create a new repo from this template. Name it whatever you'd like! 8 | 1. Open up the `.devcontainer/devcontainer.json` file and replace the `` placeholder in the `postCreateCommand` property to point at your Azure DevOps repo 9 | 10 | **From Visual Studio:** 11 | 12 | 1. Sign in with your GitHub account 13 | 1. Create a new Codespace using the repo you created above 14 | 1. If needed, you'll be prompted to sign into Azure DevOps 15 | 1. Connect to the Codespace, and start coding in the cloud 🚀 16 | -------------------------------------------------------------------------------- /TODO.md: -------------------------------------------------------------------------------- 1 | To make this repo template a reality, we'd need to do the following things (all of which is work we want to do anyways): 2 | 3 | 1. :runner: Add support for the `workspaceFolder` property in `devcontainer.json`, so that Visual Studio would automatically open the sub-repo folder upon connecting to the Codespace 4 | 5 | In order to make this flow a little bit nicer, we could also do the following things over time: 6 | 7 | 1. Enhance GitHub repo templates to accept parameters when creating a derived repo. This would allow the Azure DevOps repo to be specified via a web form, as opposed to manually editing the `devcontainer.json` file directly. 8 | 9 | 1. Provide some tooling (perhaps inside of Visual Studio?) to allow you to create new GitHub repos from a template 10 | 11 | 1. Provide a Git credential manager ("GitHub Keychain") in github.com to allow management of the Codespace from the web 12 | --------------------------------------------------------------------------------