Skip to content

Assignment Problems and Support

Jump to bottom
mike-snhu edited this page Sep 13, 2026 · 3 revisions

Assignment Problems and Support

Different questions belong in different places. Choosing the right channel helps you get a useful answer without exposing graded work or private information.

First: Check the Current Instructions

Before posting a question:

  1. Read the top-level repository README.
  2. Read the README for the Part or SDLC phase you are working on.
  3. Check this wiki for a related explanation.
  4. Search existing GitHub Issues and Discussions.

Top-level README:

https://github.com/GC-STEM/it140-m2-assignment

My Program Does Not Run

Start with the exact Python error message.

Then:

  1. Identify the file and line Python reports.
  2. Check the most recent code you changed.
  3. Compare that code with the Construct README and provided pseudocode.
  4. Correct one problem at a time.
  5. Run the program again.

Do not rewrite course-provided structures that the assignment does not ask you to change.

See Testing and Debugging.

My Program Runs but the Result Is Wrong

Return to the SRS acceptance cases:

https://github.com/GC-STEM/it140-m2-assignment/blob/main/Part-A/analysis/name_age_srs.md

Compare:

  • The input you used
  • The expected result
  • The actual result
  • The requirement being checked

Then correct the code that implements that behavior.

My Local Automated Tests Do Not Pass

Use the Test README:

https://github.com/GC-STEM/it140-m2-assignment/blob/main/Part-A/tests/README.md

If a local test fails:

  • Identify which test failed.
  • Read the corresponding acceptance case in the SRS.
  • Correct name_age.py.
  • Do not edit test_name_age.py to force a pass.

The local tests are optional and supplement the course feedback process.

The GitHub Actions Python Program Check Failed

A push that changes name_age.py can run:

IT 140 Checks → Python program check

If the check reports a Python syntax failure:

  1. Open the reported file and line.
  2. Correct the syntax problem.
  3. Run the program locally again.
  4. Commit and push the correction.

If an acceptance test fails:

  1. Identify the failed case.
  2. Compare it with the SRS.
  3. Correct name_age.py, not the provided test.
  4. Test locally and push the correction.

If the workflow itself appears broken because of a missing course file, GitHub Actions configuration error, or another problem in the provided repository, report that as a technical repository Issue.

A failed or green Actions check is not a grade and does not submit the assignment.

VS Code Shows an Error or Warning

Read the message before changing code.

Ask:

  1. Which file is the message about?
  2. Which line is involved?
  3. Is that line one the assignment allows me to change?
  4. Does the message describe a syntax problem, style concern, or another issue?
  5. Does the program actually run?
  6. What do the assignment requirements say?

Some provided source structure uses concepts you have not studied yet. Do not rewrite unfamiliar course-provided code simply because it looks advanced.

If expected extensions or workspace settings are unavailable, also check whether VS Code opened the repository in Restricted Mode. See Working in Your Course IDE.

Git or GitHub Is Not Working

Start with the exact workflow in the top-level assignment README:

https://github.com/GC-STEM/it140-m2-assignment

Common questions include:

  • Am I signed into the correct GitHub account?
  • Am I in the local clone of my personal repository?
  • Does git status show my expected changes?
  • Did the commit succeed?
  • Did the push succeed?
  • Am I looking at my personal repository rather than the public course template?
  • Did I accidentally use Fork or Use this template instead of the supported README workflow?

See Git and GitHub During the Assignment for the concepts behind the workflow.

My Repository Is Missing, Already Exists, or Is Damaged

Do not immediately delete your local folders or GitHub repository.

The current assignment README provides recovery and existing-repository options under Get Help and Support:

https://github.com/GC-STEM/it140-m2-assignment#get-help-and-support

Use the situation that matches what you see. The recovery workflow is designed to preserve existing work before replacing or recreating anything.

If you are unsure which copy contains your latest work, stop before deleting, renaming, resetting, or force-pushing anything and ask for help.

I Switched Devices and Git Reports a Conflict or Diverged History

Stop making changes on both devices.

Do not try random merge, reset, rebase, or force-push commands.

The assignment recommends one device because it is the simplest workflow. If you use more than one device, the same personal repository must be synchronized before and after each switch.

See Git and GitHub During the Assignment and the current root README.

My Course IDE Is Not Working

Module Two assumes that you completed the Module One Setup Tasks.

If the problem is with the environment itself rather than the assignment files, use:

https://github.com/GC-STEM/it140-m1-setup-tasks/wiki/Setup-Problems-and-Support

Examples include:

  • VS Code will not start
  • Python is unavailable
  • Git or GitHub CLI is missing
  • A course extension is missing across course repositories
  • The CVD is not configured
  • A local course IDE no longer verifies correctly

If a supported local environment is blocking your coursework, the CVD remains the course reference environment.

I Am Not Sure What the Assignment Is Asking

Use the sources in this order:

  1. Module Two Assignment Guidelines and Rubric in D2L Brightspace — official assignment requirements, grading, and submission
  2. Top-level Module Two repository README — repository setup, saving, Actions feedback, and submission workflow
  3. Part A or Part B README — step-by-step activity guidance
  4. Phase README — Analyze, Design, Construct, or Test instructions
  5. SRS/SDD/SDW and other provided artifacts — technical details for the current phase
  6. Wiki — supplemental explanation

If two sources appear to conflict, do not guess which requirement to follow. Contact your instructor and identify the conflicting sections.

I Have a Question About Grading

Contact your instructor through D2L Brightspace.

GitHub Issues, Discussions, and Actions are not the grading system.

Questions about the following belong with your instructor:

  • Rubric interpretation
  • Grades
  • Instructor feedback
  • Deadlines
  • Late work
  • Resubmissions
  • Accommodations
  • Academic-policy questions
  • What must be submitted

Ask a Repository Question

Use Module Two GitHub Discussions for repository-related questions when appropriate.

Before posting:

  1. Search for a similar discussion.
  2. Give the file or README section you are using.
  3. Describe what you are trying to do.
  4. Describe what you expected.
  5. Describe what happened.

Do not post your complete graded solution.

Report a Technical Repository Problem

Use Module Two GitHub Issues for problems with provided course materials or repository tools.

Useful examples include:

  • Broken link
  • Missing provided file
  • Incorrect repository path
  • Starter file problem
  • Provided test problem
  • GitHub Actions/workflow problem
  • Course-provided command that fails in a supported environment

Before reporting, collect:

  • CVD, Windows, macOS, or Linux
  • README section or step
  • File path
  • Exact command, if applicable
  • What you expected
  • What happened
  • Complete error message or Actions summary
  • Troubleshooting already attempted
  • Screenshot when useful

Protect Your Private Information

Before posting a screenshot, command output, error message, log, or Actions output, check it for private information.

Do not post:

  • Passwords
  • Authentication or verification codes
  • GitHub personal access tokens
  • Recovery codes
  • Student identification numbers
  • Private contact information
  • Other credentials or secrets
  • Complete solutions to graded assignments

If you are unsure whether something is safe to share, ask your instructor first.

Using AI for Troubleshooting

An AI assistant can help explain an error message or describe a technical concept.

For more useful help, provide information such as:

  • The exact error
  • The relevant small code section
  • What you expected
  • What happened
  • What you already tried

Do not ask an AI tool to replace work the assignment specifically requires you to complete in your own words.

If AI assistance contributes to your submitted work, follow the current assignment and SNHU acknowledgement and citation guidance.

See Sources, Citations, and AI Use.

Support Links

IT 140 Module Two Assignment

Assignment Links

Help and Course Resources

Clone this wiki locally