chore: add devcontainer config #1348
Closed
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.
Disclaimer: Experimental PR review
Greptile Summary
Updated On: 2025-09-17 11:25:51 UTC
This PR adds a minimal devcontainer configuration file (
.devcontainer/devcontainer.json) to automate the development environment setup process. The configuration includes apostCreateCommandthat runs the exact sequence of commands specified in the CONTRIBUTING.md guide: installing Poetry plugins (poetry-dotenv-plugin and poetry-bumpversion), installing all project dependencies with extra packages, and setting up pre-commit hooks.The devcontainer integration streamlines developer onboarding by eliminating the need to manually execute multiple setup commands when creating a new development environment. This automation ensures consistency across different development setups and reduces the friction for new contributors to get started with the project. The configuration follows the existing development workflow documented in CONTRIBUTING.md, making it a natural extension of the current development practices.
PR Description Notes:
Confidence score: 4/5
Context used:
Rule - Open a GitHub issue or discussion first before submitting PRs to explain the rationale and necessity of the proposed changes, as required by the contributing guide. (link)