-
Notifications
You must be signed in to change notification settings - Fork 1
Course Repositories
IT 140 uses several GitHub repositories for different purposes.
A repository, often shortened to repo, is a folder of project files managed with Git. A GitHub repository can contain code, documentation, diagrams, tests, configuration files, and a history of changes.
When you open a course repository, begin with its top-level README.md.
Repository: GC-STEM/it140
https://github.com/GC-STEM/it140
This is the central technical hub for the course. It contains course automation, course-wide configuration, development and operational status, links to activity repositories, and shared technical resources.
Do not manually clone this repository for normal course work. The course automation obtains the files it needs automatically.
Repository: GC-STEM/it140-m1-setup-tasks
https://github.com/GC-STEM/it140-m1-setup-tasks
This repository contains first-time setup instructions for GitHub and the course IDE. It is primarily an instruction and support repository rather than a graded-work repository.
Modules Two, Three, and Four each have a public course repository:
GC-STEM/it140-m2-assignmentGC-STEM/it140-m3-assignmentGC-STEM/it140-m4-assignment
These public repositories provide starter files, reference material, workflow instructions, and automated checks.
Modules Five through Seven use one public course repository:
GC-STEM/it140-projects
You create one personal Projects repository in Module Five and continue using that same personal repository through Modules Six and Seven.
For an assignment or project, you normally work with three related copies.
Example:
GC-STEM/it140-m3-assignment
This is the course-provided starting point. You can read it, but students do not complete graded work directly in this public repository.
The activity README tells you how to create a private repository in your GitHub account from the current course repository.
This personal repository stores the commits you push to GitHub.
The setup workflow also creates a local clone, normally below your Repos folder, such as:
~/Repos/it140-m3-assignment
This is the copy you open in VS Code and edit.
A useful model is:
Public course repository → your private GitHub repository → your local clone
You normally do your assignment work in the local clone of your personal repository.
The public assignment and project repositories may display GitHub controls such as Fork or Use this template.
For IT 140 student assignments and projects:
Do not select Fork or Use this template unless a current course instruction explicitly tells you to do so.
The root activity README provides the supported setup workflow. Using a different GitHub creation path can interfere with later course commands, troubleshooting, or automated checks.
For each Module Two, Three, or Four assignment, create the personal repository only once.
When you return later:
- Open the existing local clone if it is already on that device.
- If your personal GitHub repository exists but the current device does not have a local clone, clone your existing personal repository.
- Do not create another repository from the public course template simply because you changed devices.
For Projects, the same it140-projects personal repository continues across Modules Five, Six, and Seven.
Using one device for an assignment is the simplest approach and reduces synchronization problems.
If you must switch devices:
- Save, commit, and push your current work before leaving the first device.
- On the other device, use the existing personal repository.
- Synchronize from GitHub before editing.
- If Git reports a merge, history, or fast-forward problem, stop and use the activity support guidance rather than trying random reset or merge commands.
The exact commands are maintained in each activity README so they can be tested and updated in one authoritative place.
Saving work to GitHub and submitting an assignment are separate actions.
A normal workflow is:
Edit locally → save → commit → push to your personal GitHub repository → submit the required files in D2L Brightspace
GitHub provides repository history, backup, and automated feedback. D2L Brightspace remains the system for assignment submission, grading, deadlines, and instructor feedback.
Always use the current Guidelines and Rubric in D2L Brightspace and the current repository README to confirm which files must be submitted.
Assignment and project repositories may run IT 140 Checks in GitHub Actions after you push changes.
These checks can provide formative feedback about such things as:
- Python syntax or provided acceptance tests
- Whether expected student-editable files have changed
- Basic repository structure
- Course-managed file integrity
The exact checks differ by activity.
A green GitHub check is not a grade and does not submit the assignment.
Use the activity README or its CI guide for the current check names and interpretation.
Course activity repositories may be published or updated on different schedules.
For current repository availability, use the table in the main course README:
https://github.com/GC-STEM/it140
If Brightspace references a repository that is not yet available, check the main course README for its current status before reporting a problem.
Most IT 140 repositories contain one or more README.md files. A README usually explains:
- What the repository or folder is for
- What files it contains
- What you need to do
- What order to complete steps in
- Where to go next
The .md extension means the file uses Markdown, a plain-text format commonly used for software documentation.
A good habit is to read the README before running commands or changing files.
Repositories often contain files that support development, automation, testing, or course maintenance but are not part of the student activity.
For example, you may see:
- Hidden folders beginning with
. - Configuration files
- Automated test files
- Development documentation
- Scripts
- Repository metadata
Do not assume every file is something you need to edit. Follow the activity README. If it does not tell you to change a file, leave the file unchanged unless the activity explicitly allows that change.
You do not need prior Git or GitHub experience to begin IT 140.
During the course, you will gradually become more familiar with:
- Repositories
- README files
- Markdown
- Personal and remote repositories
- Local clones
- Commits and pushes
- Version control
- Project organization
These are common software-development concepts. The goal is to learn them gradually while using them to support your programming work.
- First-time course setup: https://github.com/GC-STEM/it140-m1-setup-tasks
- Main course status and activity links: https://github.com/GC-STEM/it140
- Course automation overview: Course Automation
- Questions or repository problems: Status-Issues-and-Discussions