Assignment Problems and Support

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 phase you are working on.
3. Check this wiki for a related explanation.
4. Search existing GitHub Issues and Discussions.

Repository README:

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

The Assignment Artifact Check Failed

The student-facing GitHub Actions job is:

IT 140 Checks → Assignment artifact check

If the check reports that one of your editable design files is still in the starter state, contains starter prompts, or has a basic file-format problem, use the feedback to correct your work and push the revision.

If the workflow appears broken because of a missing provided file, GitHub Actions configuration error, or another technical course-repository problem, report it through Issues.

A failed or green check is not a grade.

See Testing and Debugging.

Git or GitHub Is Not Working

Start with the exact workflow in the top-level README.

Check:

• Are you signed into the correct GitHub account?
• Are you in the local clone of your personal repository?
• Did you accidentally use Fork or Use this template?
• Does git status show the files you expected?
• Did the commit succeed?
• Did the push succeed?
• Are you looking at your personal repository rather than the public course template?

See Git and GitHub During the Assignment.

I Switched Devices and Git Reports a Conflict

Stop making changes on both devices.

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

Use the multi-device guidance in the root README and ask for help if the histories cannot be synchronized normally.

VS Code or a Course Extension Is Not Working

If the problem is limited to this repository, first check whether VS Code opened it in Restricted Mode. See Working in Your Course IDE.

If Python, Git, GitHub CLI, VS Code, or course extensions are missing or broken across course repositories, use Module One setup support:

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

Repository or Tool Problem

Use the repository's Issues area for a specific technical problem with:

• Repository instructions or broken links
• Provided starter or reference files
• Draw.io or pseudocode file behavior in the course IDE
• GitHub Actions checks
• Optional test files
• A reproducible Git/GitHub workflow problem caused by the repository instructions

Issues:

https://github.com/GC-STEM/it140-m3-assignment/issues

Include what you were doing, what you expected, what happened, and the exact error message or Actions summary when applicable.

Repository-Related Question

Use the repository's Discussions area for questions that may help other students understand the repository workflow or tools:

https://github.com/GC-STEM/it140-m3-assignment/discussions

Do not ask for or post a completed graded flowchart or pseudocode solution. Ask for resources or explanations that help you discover and correct your own solution.

Course Content Question

Post questions about course content that are not specific to this repository in your section's General Questions discussion topic or another course-approved support channel.

Submission, Grading, or Feedback Question

Contact your instructor through the course-approved D2L Brightspace channel for questions about:

• Assignment submissions
• Grades
• Rubric feedback
• Deadlines
• Accommodations
• Your individual work

Protect Private and Graded Information

Do not post publicly:

• Passwords or authentication codes
• GitHub tokens or recovery codes
• Student identification information
• Private contact information
• Complete graded assignment solutions

A screenshot can contain private information outside the area you intended to show. Review screenshots before posting them.