-
Notifications
You must be signed in to change notification settings - Fork 2
Working with Project Files in VS Code
This page explains how the IT 140 Projects repository fits into Visual Studio Code (VS Code). Follow the repository README for the current step-by-step setup and command instructions.
You use the same personal it140-projects repository across:
- Module Five — Project One design
- Module Six — milestone prototype
- Module Seven — Project Two final game
Do not create a new project repository for each module.
Your project normally has three related copies:
-
Public course repository —
GC-STEM/it140-projects, which provides starter files and instructions. -
Your private personal GitHub repository —
it140-projectsin your GitHub account, which stores work you push to GitHub. -
Your local clone — normally
~/Repos/it140-projects, which you open in VS Code and edit.
Do not select Fork or Use this template on GitHub. Follow the root README to create or open your personal repository correctly.
Open the repository root in VS Code rather than opening only one project file or one subfolder. This keeps the complete three-module project structure visible and makes the course workspace settings and recommended extensions available.
The repository contains folders such as:
-
analysis/— shared requirements -
design/— Project One design work -
prototype/— Module Six milestone work -
src/— Project Two final game work -
tests/— testing resources
The exact graded files differ by module. Follow the current D2L Brightspace Guidelines and Rubric and the root README for the module you are completing.
Your ~/Repos folder should already be trusted if you completed the Module One course IDE setup.
If VS Code opens in Restricted Mode, follow the current root README instructions and trust the entire Repos folder rather than only it140-projects. VS Code applies that trust to repositories below the trusted parent folder.
After the folder is trusted, course extensions and workspace settings should be available normally.
The repository README contains command blocks labeled bash.
Windows users should run those Bash command blocks in Git Bash, not PowerShell or Command Prompt.
The exact commands remain in the root README because those command blocks are maintained and tested with the repository.
The course workspace recommends extensions that support the file types used throughout the project, including:
- Python development, debugging, and environment support
- Ruff code-quality feedback
- Pseudocode viewing and editing
- Draw.io diagram viewing and editing
- Markdown editing and preview support
- Spelling support for comments and documentation
You do not need to memorize the extension list. If VS Code shows Workspace Recommendations, those recommendations come from the course repository configuration.
Saving a file in VS Code writes the change to your local clone. It does not automatically save that change to GitHub.
Periodically commit and push your work so your private personal GitHub repository contains a current backup. Follow the root README for the current commands and for the safest workflow if you use more than one device.
Your local clone is where you work. Your personal GitHub repository stores work you push. Neither replaces the assignment submission in D2L Brightspace.
Submit the files required by the current Guidelines and Rubric in D2L Brightspace.