Remove .vscode folder to prevent VS Code settings conflicts#36
Merged
Conversation
- Deleted .vscode/settings.json that was forcing git signing settings - .vscode/ is already in .gitignore to prevent future additions - This prevents the repository from overriding individual developer VS Code preferences
Contributor
There was a problem hiding this comment.
Pull Request Overview
This is a version bump release from 1.5.0 to 1.6.0, with repository cleanup to properly enforce existing gitignore rules.
- Version bumped to 1.6.0 in package.json and package-lock.json
- Removed .vscode/settings.json (should have been gitignored)
- Added test-workspace/ to .gitignore for test artifact cleanup
Reviewed Changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Version bumped from 1.5.0 to 1.6.0 |
| package-lock.json | Lockfile version updated to match package.json |
| .vscode/settings.json | Removed editor-specific settings file (already covered by .gitignore pattern) |
| .gitignore | Added test-workspace/ directory to ignore test artifacts |
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
Explain the change in 1–3 sentences. Reference any related issues (e.g. Closes #123).
Type of Change
Motivation / Context
Why is this change needed? What problem does it solve or what capability does it add?
Approach
Briefly describe how you implemented the change. Note any notable design decisions, trade-offs, or alternatives considered.
CLI Impact
If this alters user-facing CLI behavior:
Generated Output Impact
List any new / modified scaffold files or structural differences (e.g. new template folder, changed Dockerfile pattern, compose changes, new preset behaviors).
Tests
Describe test coverage:
If you ran the smoke scaffold locally, paste the command & confirm success:
Result: ✅ / ❌
Screenshots / Logs (Optional)
Add any helpful output (chalk-styled CLI messages, error reproduction, etc.).
Docs
README.mdif needed.github/copilot-instructions.mdif internal conventions changedChecklist
templates/Open Questions / Follow-ups
List any TODOs or future enhancements not in this PR.
Thanks for contributing! 🎉