-
Notifications
You must be signed in to change notification settings - Fork 554
[1139] Fixed Code Spells #1140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[1139] Fixed Code Spells #1140
Conversation
samruddhikhandale
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wow! Thank you for taking the time in correcting these 🙌
89280f4 to
6c8a039
Compare
|
I have updated all the feature versions. Please take a moment to review them thoroughly. Thank you! |
6c8a039 to
3541013
Compare
6c8bcea to
ce84d6e
Compare
|
Hi @samruddhikhandale , I have updated all the feature versions. Please take a moment to review them thoroughly. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request addresses spelling errors found throughout the repository's code comments, documentation, and feature descriptions. The changes improve code readability and professionalism by correcting various typos.
Key Changes:
- Fixed spelling errors in comments across multiple shell scripts (install.sh files and test scripts)
- Corrected feature description spelling in docker-outside-of-docker
- Removed trailing whitespace in test files
- Bumped version for java feature to 1.6.4 to reflect the changes
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| test/powershell/install_powershell_fallback_test.sh | Fixed "validaiton" → "validation" and removed trailing whitespace |
| test/kubectl-helm-minikube/checkBashCompletion.sh | Fixed "atomatically" → "automatically" in comment |
| test/aws-cli/checkBashCompletion.sh | Fixed "atomatically" → "automatically" in comment |
| src/python/install.sh | Fixed "alises" → "aliases" in comment |
| src/node/install.sh | Fixed "apears" → "appears" and "compatiblity" → "compatibility" in comments |
| src/java/install.sh | Fixed "apears" → "appears" in comment and removed trailing whitespace |
| src/java/devcontainer-feature.json | Bumped version from 1.6.3 to 1.6.4 |
| src/docker-outside-of-docker/devcontainer-feature.json | Fixed "Re-use" → "Reuse" in description |
| src/docker-outside-of-docker/README.md | Fixed "Re-use" → "Reuse" in description |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -1,9 +1,9 @@ | |||
| { | |||
| "id": "docker-outside-of-docker", | |||
| "version": "1.6.5", | |||
Copilot
AI
Dec 29, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version should be bumped when making changes to a feature, even for documentation-only changes like this description fix. According to the CONTRIBUTING.md guidelines, features should follow semantic versioning (semver), and description changes in distributed packages typically warrant a patch version bump. Consider incrementing to version "1.6.6".
| "version": "1.6.5", | |
| "version": "1.6.6", |
Issue: #1139
Overview: This pull request addresses various spelling errors found in the code comments across the repository. The goal is to enhance readability and maintainability, ensuring that our documentation is clear and professional.
Changes Made:
Corrected spelling mistakes in comments throughout the codebase.
Impact: These changes should help team members and future contributors understand the code more easily, reducing the potential for confusion and improving overall code quality.
Additional Notes: I recommend reviewing the changes to ensure all comments are now accurate and clear. Let me know if there are any additional areas that need attention!