autogen
autogen copied to clipboard
Add dev container for AutoGen Studio
Solution:
Create a subdirectory called .devcontainer/studio
with correct Dockerfile
and devcontainer.json
.
I reused the Dockerfile from .devcontainer
and modified the devcontainer.json
to follow instructions from AutoGen Studios README.
I tested this container with GitHub Codespaces.
Why are these changes needed?
We need to add a dev container for AutoGen Studio
Related issue number
#1224
Checks
- [ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
- [ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
- [ ] I've made sure all auto checks have passed.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
bde2fc9
) 32.10% compared to head (775226a
) 32.10%.
Additional details and impacted files
@@ Coverage Diff @@
## main #1241 +/- ##
=======================================
Coverage 32.10% 32.10%
=======================================
Files 32 32
Lines 4392 4392
Branches 1024 1024
=======================================
Hits 1410 1410
Misses 2866 2866
Partials 116 116
Flag | Coverage Δ | |
---|---|---|
unittests | 32.05% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@victordibia I need your help to add a relevant reviewer to this PR.
How do we use it? If I open a GitHub codespace I don't get to choose which Dockerfile to use, do I?
How do we use it? If I open a GitHub codespace I don't get to choose which Dockerfile to use, do I?
Use the "new with options"
How do we use it? If I open a GitHub codespace I don't get to choose which Dockerfile to use, do I?
Use the "new with options"
![]()
Thanks. Could you add this info to documentation?
LGTM except that documentation is missing. I am fine merging this PR. We could add documentation in a separate PR.
Ty, working on that issue