Add codespaces configuration#26137
Conversation
|
Argh, sorry I've messed up the labels. |
|
I'd be happy to merge just so you can make progress testing it in situ, with the understanding you will keep an eye on it and field questions in the unlikely event someone jumps on this before it's fully baked. |
|
That's the plan, I'd also like to get some feedback from potential users on the configuration and I'll be also drafting the docs in the meantime. |
|
I see this was already approved. I think for infrastructure things like this it's ok for one review at least until it's in wide use. Particularly as we all were ok with doing this in principal. |
|
This is mind-blowingly good! How to getflux box up needs a bit of documentation. If we can not auto-activate the right conda env, we should drop a Lets see if I can do this from inside a codespace.... |
PR summary
This pull request adds a GitHub codespaces configuration for Matplotlib. With this PR, contributors can open a pre-configured development environment and get started with contributing to Matplotlib right away from their browser. I'm not sure if you can test it as it is, as I believe this needs to be merged to main before anyone is able to open a codespace from the Matplotlib repo.
Once this is merged, it will enable users to go to matplotlib/matplotlib or their own fork and choose "Create codespaces on
<branch>":This will open a browser window with a VSCode interface and a pre installed development environment built over an Ubuntu image. Users can then do
After that you can run tests, build the documentation and run other commands.
This configuration also includes a lightweight fluxbox environment
To be done in a follow-up: documentation on how to use it and current features (like connecting to the fluxbox desktop to see plots).
PR checklist