Codespaces proof-of-concept

[ian-r-rose]

Fixes #203

Would appreciate feedback from @britt-allen or @matthewzhou. There is some documentation for how to set things up here

[ian-r-rose]

These are the secrets that you need to set in order to do dbt-related work in the codespace

[ian-r-rose]

Caught some real bugs in the pre-commit set-up when doing this!

[ian-r-rose]

Drive-by change, organizing some of the dbt-related docs into a folder

[britt-allen]

There are no instructions for what to do after you get to this screen. This screen comes immediately after clicking "New with options..." @ian-r-rose I assumed I should create a new branch so I did that and left the other defaults untouched.

[britt-allen]

I did not have an option to add "Recommended Secrets" as the docs say immediately following creation of a codespace with options. This is the screen (below) I was taken to immediately after. It's unclear if I should expect to see the form listed in the docs or if I have to navigate to it. If the latter the instructions are lacking.

[ian-r-rose]

Did you try to create the codespace from the devcontainer branch?

[ian-r-rose]

You should go to the devcontainer branch to create the codespace. If this is in main, that step will not be necessary, so it seemed incorrect to add it to the docs

[britt-allen]

Wow this was SO easy, I am not sure whatever magic you did in the background, but this just works. Thanks @ian-r-rose. I cannot wait to show this off to future MDSA trainees.

One question the docs doesn't answer: "Should we let Visual Studio Code periodically run git fetch?" this is a pop up I got while using codespaces. Want to provide guidance, but seems like it's a personal preference thing. If I do have git fetch running in the background can I still run git pull to get changes into my working directory or will I only be able to use git merge since git fetch is being run?

[ian-r-rose]

Thanks for testing it out!

One question the docs doesn't answer: "Should we let Visual Studio Code periodically run git fetch?" this is a pop up I got while using codespaces. Want to provide guidance, but seems like it's a personal preference thing.

To be honest, I'm not sure what to recommend here, I don't really understand what the VS Code git extension does when you say yes. I suspect you are right that it's a personal preference thing, though I usually avoid automated git actions because (in my experience) it's an easy way to get into trouble with your git history.

If I do have git fetch running in the background can I still run git pull to get changes into my working directory or will I only be able to use git merge since git fetch is being run?

I think you should still be able to run normal git operations, even if the extension is also doing things occasionally in the background. But I'm not 100% sure, having not really experimented with it myself.