Expose local files in Codespaces - #256
Merged
Merged
Conversation
krowvin
marked this pull request as ready for review
August 11, 2026 20:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PYTHONPATHWhy
The post-create Poetry install prepares the project and development dependencies, but processes started outside the repository working directory do not consistently discover repository-local source and test files. Exposing
${containerWorkspaceFolder}throughPYTHONPATHmakes the local checkout available across the Codespace.Impact
Edits to source and test files are immediately reflected in Python processes anywhere in the dev container. Normal package installation and the existing virtual environment layout are unchanged.
Validation
/tmpconfirmedcwmscliandtestsresolve under/workspaces/cwms-clipoetry run pytest -q(373 passed)poetry run pre-commit run --all-files