-
Notifications
You must be signed in to change notification settings - Fork 0
Assignment Problems and Support
Different kinds of problems need different kinds of help. Choosing the right support path can save time and protect your graded work.
Contact your instructor through D2L Brightspace when your question is about:
- what the assignment requires;
- how the rubric will be applied;
- whether a particular pseudocode design satisfies the assignment;
- instructor feedback; or
- a course-specific exception or accommodation.
The current Module Four Assignment Guidelines and Rubric and your instructor take priority over repository or Wiki explanations.
Use GitHub Discussions for questions such as:
- how to use a provided repository file;
- how to open a file in VS Code;
- what a repository instruction means; or
- how the optional practice tools are intended to work.
Do not post a completed graded pseudocode solution publicly.
Use GitHub Issues to report a reproducible technical problem with:
- a provided starter file;
- a broken repository link;
- documentation;
- a GitHub Actions check;
- the optional test file; or
- repository configuration.
A useful report includes:
- what you were trying to do;
- what you expected;
- what happened instead;
- the exact error message, if any;
- whether you are using the CVD, Windows, macOS, or Linux; and
- enough detail to reproduce the problem without sharing your completed graded solution.
If the problem is with the course IDE rather than the M4 assignment files, return to the Module One Setup Tasks.
Examples include:
- GitHub authentication is not working;
- VS Code extensions are missing;
- Git or GitHub CLI is unavailable; or
- a local computer was not configured through the course setup process.
Start with:
gh auth statusConfirm that the GitHub account you use for IT 140 is active.
If it is not, follow the GitHub section of the Module One Setup Tasks rather than repeatedly running assignment repository-creation commands.
If GitHub reports that it140-m4-assignment already exists, you probably already created your personal repository.
Do not immediately delete it.
Instead:
- check your GitHub account for the existing private repository;
- check
~/Reposfor the local assignment folder; and - open the existing work if it is the copy you want to keep.
The repository README contains safe restore/restart procedures when a fresh copy is actually needed.
That is okay. A .pseudo file is a text file.
The important requirements are the logic, input/output, decision branching, loops, indentation, and clarity described by the assignment—not a particular visual editor appearance.
Open the most recent Assignment Checks run and read the failed step.
Common reasons while working include:
- the graded pseudocode is still unchanged from the starter;
- pseudocode TODO prompts remain;
- a course-provided file was changed; or
- a required file is missing.
A red X does not itself determine your assignment grade.
If you chose the optional construction practice, compare the failing behavior with:
- the SRS;
- your pseudocode; and
- your Python program.
Correct the first artifact that is wrong. Do not edit the course-provided test just to make it pass.
Before any destructive recovery step:
- save your files;
- commit and push good work when possible; or
- make a backup copy of the local repository folder.
Do not delete or overwrite a working repository simply because a command reports that something already exists.
| Question/problem | Best starting point |
|---|---|
| Assignment requirement or grade | Instructor / D2L Brightspace |
| Repository-use question | GitHub Discussions |
| Technical defect in provided repo content | GitHub Issues |
| Course IDE setup/authentication | Module One Setup Tasks |
| Optional testing/debugging | Testing and Debugging |
Return to Home.