Your capstone project is probably the single best piece of work you will finish in your entire time at NOVA. Here is the catch: if it lives on your laptop, it does not exist to the hiring manager reading your resume. GitHub is where you put the thing so they can look at it and say, "Yeah, this person can actually build software."
1
Proof of workThe link on your resume that makes recruiters click.
2
A portfolioEvery repo is a project you can point to for years.
3
Version controlNever lose work. Every change is saved forever.
4
Live websitesGitHub Pages gives you a real URL for free.
90% of IT and web development jobs expect you to use Git or GitHub on day one. The ones that do not, will. Learning this now means you walk into your first job already fluent in the most common tool your team uses.
The two questions everyone asks first
Is it free for NOVA students?
Yes. GitHub itself is free for everyone, and NOVA students get the GitHub Student Developer Pack on top of that — which adds free GitHub Pro, free Copilot, and a pile of free developer tools. You verify with your @email.vccs.edu address and the whole process takes about five minutes.
Can I keep my code private?
Yes. Private repositories are free for every GitHub account, student or not. Nobody but you (and the people you invite, like your professor) can see the code. You can build your capstone in private, then flip it public the moment it is graded. See the privacy section below for the exact steps.
If my repo is private, can I still get a live website URL?
Yes, with the Student Pack. A live GitHub Pages URL (like yourname.github.io/capstone) from a private repo is a GitHub Pro feature. The Student Pack gives you Pro for free, so NOVA students get this at zero cost. The source code stays locked down and the live site is still reachable by anyone with the URL. Without the Student Pack on a totally free account, Pages only works from public repos.
What if I want the website itself to be private too?
That costs money. Making the Pages site access-controlled so only invited people can view it (not just access the code) is a GitHub Enterprise feature. For a student capstone you almost never need this — "public live site, private source code" is the standard setup, and that is the one the Student Pack gives you for free.
The short versionFree account → claim the Student Pack → create a private repo → build your capstone in peace → publish a live Pages URL while the code stays private → flip the source to public the day it is graded. Everything in that chain is free for a NOVA student. The only thing that would cost money is hiding the live website itself behind a login, and you probably do not need that.
Shared Step 1: Create your GitHub account
NOVA student shortcut
Before you sign up — grab the GitHub Student Developer Pack
Because you are a NOVA student, GitHub will give you free GitHub Pro, which is the version that includes unlimited free private repositories with room for collaborators. This is the best way to keep your capstone locked down while you build it, and then flip it public once it is graded. It is free, it takes about 5 minutes, and you can use your NOVA email (@email.vccs.edu) to verify instantly.
Already have a GitHub account? You can still claim the Student Pack on your existing account — skip to the Student Pack walkthrough. If you are creating a brand new account, finish the six steps below first, then come back and claim the pack.
Go to github.com
Open your browser and type github.com in the address bar. Click the green Sign up button in the top right.
Use an email you will still have after graduation
Not your school email. Use a personal Gmail, Outlook, or similar. Your NOVA email will stop working after you leave, and you do not want to lose access to your portfolio.
Pick a username you can put on a resume
This becomes part of your URL forever, like github.com/your-name. Use your real first and last name or initials. No xXGamerDude420Xx. Hiring managers are going to see this.
Create a strong password
Long, unique, not reused from any other site. A password manager like Bitwarden (free) makes this easy.
Verify your email
GitHub sends you a code. Type it in or click the link in the email. This takes 30 seconds.
Turn on two-factor authentication
Settings → Password and authentication → Enable 2FA. Use an authenticator app (Google Authenticator, Authy, or 1Password). GitHub is going to require this soon anyway — do it now and get it over with.
Pro tipAdd a profile photo and a one-line bio. "Information Systems student at NOVA, building my home lab and learning Python." Takes two minutes. Makes your profile look real.
Shared Step 1.5: Claim the GitHub Student Developer Pack
This is the single most important thing to do before you touch a repository. The GitHub Student Developer Pack is free for verified students and it unlocks GitHub Pro — which is the tier that includes unlimited private repositories. Without it, you can still make private repos, but you will bump into collaborator and feature limits on the free tier. With it, you get the full thing for zero dollars, for as long as you are a student. For verification, use your class schedule. They will probably not accept your student id.
What you actually get
GitHub ProUnlimited private repositories, unlimited collaborators on those private repos, and priority support. This is the main one you care about for your capstone.
GitHub Copilot ProAI pair programmer inside VS Code and the GitHub web editor. Free for students while enrolled.
NamecheapOne free .me domain for a year. Pair it with GitHub Pages and you have a real portfolio URL like yourname.me.
DigitalOcean$200 in hosting credit. Enough to run a real project for a semester.
JetBrains IDEsFree PyCharm Pro, WebStorm, IntelliJ Ultimate, and the rest of the JetBrains family while you are a student.
Canva Pro, Bootstrap Studio, Termius, and dozens moreDesign tools, SSH clients, API clients, learning platforms. The full list is on the Student Pack page and changes over time.
How to sign up — step by step
Go to education.github.com/pack
Open https://education.github.com/pack and click the Sign up for Student Developer Pack button near the top of the page. If you are not already logged in, GitHub will ask you to log in to the account you just created.
Choose "Student" on the application form
GitHub will ask whether you are a student or a teacher. Pick Student. This takes you to the Global Campus benefits application.
Add your NOVA school email
On your GitHub account settings, go to Emails and add your NOVA email address (the one that ends in @email.vccs.edu). Verify it by clicking the link GitHub sends you. This is the fastest way to get approved — the .edu-style address is how GitHub knows you are a real student.
Fill out the application
Pick Northern Virginia Community College from the school dropdown. Enter your graduation date (rough estimate is fine). Write one short sentence about what you plan to use GitHub for — something like "I am building my capstone project for ITP 120 and want to use GitHub to manage my code and eventually publish a portfolio."
Upload proof if GitHub asks
Most NOVA email addresses get auto-approved. If GitHub asks for extra proof, upload a photo of your student ID, a class schedule, or a transcript screenshot that clearly shows your name and the current term. Blur out any sensitive numbers before you upload — only your name and "Northern Virginia Community College" need to be visible.
Wait for the approval email
Approval is usually instant with a verified NOVA email. If GitHub needs to look at your ID manually it can take a few days. You will get an email when you are approved, and GitHub Pro will just start working on your account — no extra install, no payment info required.
Verify Pro is active
Go to your profile in the top right, then Settings → Billing and plans. You should see GitHub Pro listed as your current plan. That is the confirmation that unlimited private repos are unlocked.
Why this is the best path for capstonesFree private repo means you can develop your capstone in peace without anyone looking over your shoulder at messy in-progress code. Commit early, commit often, break things, fix them — nobody sees until you are ready. Once the capstone is graded, flip it to public in 30 seconds and suddenly you have a professional portfolio link on your resume.
The two-email trick — so your account outlives graduation
Here is the part nobody explains clearly. A GitHub account can have more than one email address attached to it. You use that on purpose: your personal email is the one that owns the account forever, and your NOVA email is just a verification badge that unlocks the Student Pack. When you graduate, you peel the NOVA email off and the account keeps going exactly as it was.
Primary email = your personal email
Sign up for GitHub using your personal Gmail, Outlook, or iCloud address. This is the email your account is owned by. Your username, every repo, every URL, and every commit is tied to this account for the rest of your life. Do not sign up with your NOVA email as your primary.
Secondary email = your @email.vccs.edu address
On github.com, go to Settings → Emails and click Add email address. Add your NOVA email. GitHub sends a verification link — click it. Your NOVA email is now attached to the account as a secondary email. This is the one that makes the Student Pack application work.
Apply for the Student Pack
GitHub sees the verified NOVA email on your account and flips on GitHub Pro + all the Student Pack perks. You do not need to move your primary email, change your username, or migrate anything.
Re-verify once a year while you are still at NOVA
GitHub emails you every 12 months with a re-verification link. It is a two-click refresh. Do it while your NOVA email still works and you keep the benefits rolling.
When you graduate, remove the NOVA email
Once your NOVA email is about to shut off, go back to Settings → Emails and delete it from the account. Your GitHub account, your username, your repos, your commits, your Pages sites, and every URL on your resume all stay exactly the same. The only thing that changes is that Pro-only features roll back to the free tier. Private repos are still free — those are not a Pro feature anymore.
The one-line summaryPersonal email owns the account forever. NOVA email is a sticker you put on temporarily to unlock free Pro. Peel the sticker off at graduation and everything keeps working.
A couple of small gotchasThe Student Pack is tied to your individual GitHub account, so do not sign up on a shared computer lab account. If you forget to re-verify and your benefits lapse, nothing is deleted — your private repos and all your history stay put, you just lose Pro-only extras until you reverify. And once you are no longer a student at all, that is fine too: the free tier still includes unlimited free private repositories.
A repository (or "repo") is just a folder for a project. Each project you build gets its own repo. Your capstone is one repo. Your home lab notes are another repo. Your portfolio site is another repo.
Click the green "New" button
From any page, click the + icon in the top right, then New repository. Or go directly to github.com/new.
Name it something a human can read
Use lowercase with dashes. Examples: capstone-inventory-app, nova-portfolio-site, home-lab-setup. Do not put spaces in the name, and do not call it project1.
Write a one-sentence description
Example: "NOVA ITP 120 capstone — an inventory tracking app built with Python and SQLite." This shows up under your repo name and helps visitors understand what they are looking at.
Choose Public or Private
This is the big decision. Read the privacy section below for my recommendation. Short version: if nothing in it is embarrassing or secret, go Public so it shows up on your profile. Otherwise start Private.
Check "Add a README file"
This creates a file that shows up on your repo's front page. You will edit this later to explain what the project does.
Click "Create repository"
Done. You now have an empty repository waiting for your files.
Class starter code
Did your instructor give you a starter repo?
Some classes hand out starter code — a pre-built GitHub repo you download, work on, and turn in. If your instructor told you the name of a repo (in your syllabus, in class, or in an announcement), this section is for you. If not, skip this and keep going to Choose your path.
The repo name comes from your instructor
<repo-name>
Your instructor will tell you the exact name. It looks something like ite170-capstone-sp26 or itp120-final-project. Anywhere you see <repo-name> in the steps or commands below, replace it with the real name from your syllabus. The instructor's GitHub username is drjulsgilliam, so the full URL will look like github.com/drjulsgilliam/<repo-name>.
Pick how you want to get the code
There are three ways to grab a starter repo. Pick one based on what you are comfortable with — all three end with the same files on your computer.
Easiest — no install
Option 1: Download ZIP
Works 100% in your web browser. No Git, no terminal, no account required (for public starter repos).
Open github.com/drjulsgilliam/<repo-name> in your browser.
Click the green <> Code button near the top right of the file list.
In the dropdown, click Download ZIP.
Unzip the file on your computer. You will see a folder named <repo-name>-main. That is your starter code.
Rename the folder to whatever you want (for example my-capstone) and open it in VS Code.
Best for: Path A students, first-time Git users, anyone who just wants the files and does not need version history.
Heads up: a ZIP gives you the files but not the Git history. If you want to commit and push your own progress back to GitHub, you will still need to turn your folder into a new repo (see "After you get the code" below).
Recommended — own copy on GitHub
Option 2: Use this template
If your instructor marked the repo as a template (you will see a green Use this template button), this is the cleanest option — it creates a brand new repo on your GitHub account that is a fresh copy of the starter.
Open github.com/drjulsgilliam/<repo-name>.
Click the green Use this template button → Create a new repository.
Owner = you. Give it a new name like <repo-name>-yourlastname or my-capstone.
Set it to Private (you have free private repos from the Student Pack).
Click Create repository from template. Done — you now have your own copy on GitHub with its own history.
To get the files on your computer, use Path A's upload/download flow or Path B's git clone command against your new URL.
Best for: anyone who wants their work tracked on GitHub from day one — which you should, because that is how you share it with me at the end.
If there is no "Use this template" button: the repo is not a template. Use Option 1 or Option 3 instead.
Power move — command line
Option 3: Clone with Git
For Path B students who already did the command line tutorial. This is what real developers do.
Open a terminal and cd into the folder where you keep your projects.
If the starter repo is private and your instructor invited you, Git will ask for your GitHub username and a Personal Access Token the first time.
cd <repo-name> and open the folder in VS Code with code .
Best for: Path B students and anyone who wants full Git history from the start.
Important: after cloning, the remote origin still points at my repo, which you cannot push to. To push your own work back to GitHub, you need to either (a) re-point origin at your own new repo, or (b) start fresh with Option 2.
After you get the code — making it yours
However you got the files, the next step is the same: turn the starter code into your repo on your GitHub account, so you can commit your progress, back up your work, and submit it at the end of the semester.
Create a brand new private repo on your account
Follow the Create a repository steps above. Name it something like <repo-name>-yourlastname. Start it Private. Do not check "Add a README" — your starter code already has one.
Get the starter files into your new repo
Path A: On your new repo page, click Add file → Upload files, drag the unzipped starter folder's contents in, and commit. Path B: In your local starter folder run git remote set-url origin https://github.com/YOUR-USERNAME/<repo-name>-yourlastname.git then git push -u origin main.
Invite me as a collaborator
Once you have code worth grading, jump down to Share your capstone with your professor and add drjulsgilliam under Settings → Collaborators. I will then be able to see every commit you make from that point forward.
Commit often
Every time you finish a small chunk of work, commit it with a short message like "Add login form" or "Fix broken image". This is not only good practice — it is also how I can see that you worked on it steadily instead of in one panic session the night before it is due.
Quick cheat card for the capstoneThe instructor's GitHub is drjulsgilliam. The starter repo name comes from your syllabus (example: ite170-capstone-sp26). Full URL: github.com/drjulsgilliam/<repo-name>. Easiest way to get the code: green <> Code button → Download ZIP. Cleanest way: Use this template if the button is there. Power move: git clone https://github.com/drjulsgilliam/<repo-name>.git.
Now choose your path
Your account is made, your Student Pack is claimed, your repo exists. Now pick one of these two tutorials and follow it start to finish. Do not try to do both at once — it will just get confusing.
This is the most common concern students bring up, and it is a completely fair one. Let me walk you through your options.
Your three choices
Easiest for capstones
Private repo
Only you can see it. Nobody else. You can invite specific people (like your professor) by username and they will get access, but the rest of the world is locked out.
Zero stress about "who can see my messy code"
You still get all the version history and backup benefits
You can invite your professor or teammates one by one
Without the Student Pack, the free tier caps collaborators on private repos — so make sure you claimed the pack first
Public repo
Anyone on the internet can read your code, but nobody can change it without your permission.
Shows up on your profile for recruiters
You can share the link on your resume
Free GitHub Pages live site
Requires you to clean it up before showing
Cannot contain passwords, API keys, or personal info
My honest advice: start private. Build your capstone in peace. When it is finished and graded, do one cleanup pass (remove any passwords, write a real README, delete dead code), then switch it to public. You get the best of both.
How to switch private to public later
Go to the repo's Settings tab
Top right of the repo page.
Scroll all the way to the bottom
There is a section called "Danger Zone" in red. Do not panic — this is normal.
Click "Change repository visibility"
Then pick Public and confirm by typing your repo name.
The one rule about clean code
Before going public, always check for:Passwords or API keys hard-coded in files. Any .env file. Real names, emails, or phone numbers of people in test data. Database connection strings with real credentials. If you find any of these, delete them, commit the deletion, AND rotate those credentials — because the old version still lives in your history.
Capstone submission
Share your capstone with your professor
This is how you actually hand your project in. Your repo is private, so nobody can see it unless you specifically invite them by their GitHub username. You invite your professor exactly like you would invite a teammate. Once they accept, they can read everything you put in the repo — files, commits, README, and the full history of your work.
For this class — invite me at this username
drjulsgilliam
Type exactly this in the Add people search box. My profile photo and name should pop up. Click my name to select me, then click the button to add drjulsgilliam as a collaborator with Read access. My profile is at github.com/drjulsgilliam.
Getting started — the whole flow in one picture
1
Use my usernameFor this class, invite drjulsgilliam (that is me).
They acceptThey get an email + GitHub notification and click Accept.
4
Send the linkPaste your repo URL in your submission so they know where to look.
Step by step — how to invite Dr. G (or any professor)
Use my GitHub username
For this class, my GitHub username is drjulsgilliam. That is what you type in the search box — not my email, not my real name. My profile lives at github.com/drjulsgilliam. If you are using a different course or professor, ask them for their GitHub username the same way (the part after github.com/ on their profile page).
Open your private repo on github.com
Go to github.com/your-username/your-repo. Make sure you are signed in as yourself, not a shared lab account. You should see a small gray Private badge next to the repo name.
Click the Settings tab
It is in the top right of the repo menu bar, all the way over on the right side. If you do not see a Settings tab, you are probably looking at somebody else's repo, not your own.
Click "Collaborators" in the left sidebar
In the left sidebar of the Settings page, look under Access for the link that says Collaborators. Click it. GitHub will ask you to re-enter your password just to confirm it is really you.
Click the green "Add people" button
A search box pops up. Type drjulsgilliam in the box. After a second, GitHub will show my profile photo and real name underneath. Click my name to select me — do not just press Enter on a raw string, or GitHub will try to invite a brand new user at that email address.
Click "Add drjulsgilliam to this repository"
A confirmation box appears. Leave the permission set to the default (Read is fine for grading — I can see everything but cannot change your code). Click the button to confirm.
Wait for me to accept
GitHub instantly sends me an email and puts a notification on my GitHub home page. Until I click Accept, drjulsgilliam will show up under "Pending invitations" on your Collaborators page. Once I accept, I move up to "Collaborators" and I can see your repo immediately. If it has been more than a day, ping me — the invitation email sometimes lands in spam.
Send them the repo URL with your submission
Paste the repo URL (looks like https://github.com/your-username/your-repo) into your capstone submission, Canvas assignment, or email. That is the link they will click to find your work. The link will not work for anyone else — only for the collaborators you invited.
How to check that it actually workedGo back to Settings → Collaborators. You should see drjulsgilliam listed under the "Collaborators" heading (not "Pending invitations"). If it still says Pending after a day, send me a quick message — the invitation email sometimes lands in spam, and I may need to accept it from the notification bell on github.com instead.
What your professor actually does once they have access
Your professor has three different ways to look at your code. It is helpful to know all three so you can troubleshoot if something does not work on their end. The good news is you, the student, do not have to do anything extra for any of these — all three automatically work the moment your invitation is accepted.
Web browser Easiest
They just go to your repo URL and click around. GitHub lets them open any file in the browser, see the commit history, view line-by-line changes between commits, and leave comments on specific lines of code.
Best for: reading your code, checking your README, leaving written feedback.
Download ZIP No install
On your repo page they click the green Code button → Download ZIP. They get your whole project as a single zip file they can unpack on their computer and run locally.
Best for: running your code without touching Git.
Clone with Git Command line
If they use Git on the command line, they run git clone https://github.com/your-username/your-repo.git. Because the repo is private, Git asks them to sign in with a Personal Access Token or SSH key the first time.
Best for: running your code and pulling in new commits you push.
Make it easy for themBefore you submit, do these three things and your professor will be able to grade your work in minutes: (1) Write a real README with a one-sentence description and a "How to Run It" section. (2) Make sure your main file is named something obvious like index.html or app.py. (3) Include a screenshot in the README so they know what the finished app should look like. You will get better feedback and a better grade because you reduced the friction.
What if you do not want to share the whole repo?
If your capstone has stuff in it you really do not want your professor to see (old drafts, failed experiments, credentials you forgot to delete), you have two clean options:
Option 1: Make a fresh "submission" repo
Create a brand new private repo called something like capstone-final-submission, upload only the files you want graded, write a clean README, and invite your professor to that repo instead of your main working repo. This is the safest way.
Option 2: Clean your history before inviting
Delete any sensitive files, commit the deletion with a clear message, and then rotate any credentials you accidentally committed — because the old version still lives in your commit history. Only invite your professor once you are sure the current state is clean.
Cheat sheet — save this page
When you forget what something means, come back here. This is the whole tutorial compressed into one page you can print or bookmark.
GitHub Basics at a Glance
Repository (repo)A folder for one project. Every project gets its own repo.
CommitA saved snapshot of your project with a short message describing what changed.
README.mdFront page of your repo. Use: title, one-line pitch, screenshot, features, tech stack, how to run, what you learned, credits.
Change private to publicSettings → scroll to Danger Zone → Change visibility.
Good commit messageShort, present tense, specific. "Fix broken nav link" not "Stuff."
Never commitPasswords, API keys, .env files, real personal data.
2FATwo-factor authentication. Turn it on. Use an authenticator app, not SMS.
Git command line — the commands you will actually type
If you are on Path B (command line), these are the commands you need. If you are on Path A (web browser), you do not need any of these — but bookmark them for later, because every real job uses Git on the command line.
One-time setup — run these once, ever, on each computer
git config --global user.name "Your Name"Tells Git who you are. Shows up on every commit.
git config --global user.email "you@example.com"Use the email on your GitHub account so commits get linked to your profile.
git config --global init.defaultBranch mainMakes new repos use main instead of master.
Starting a project — pick one of these
git clone https://github.com/drjulsgilliam/repo-name.gitDownload an existing GitHub repo to your computer. Creates a new folder.
git initTurn a folder on your computer that already has files into a Git repo.
git remote add origin https://github.com/username/repo-name.gitAfter git init, point your local repo at a GitHub repo. Do this once per project.
The daily loop — 95% of what you do every day
git statusShow what files changed, what is staged, what is not. Run this constantly.
git add .Stage every changed file in the current folder. Means "I want these in my next commit."
git add index.html style.cssStage specific files only. Better habit than git add . on real projects.
git commit -m "Fix broken nav link"Save a snapshot with a message. Short, present tense, specific.
git pushSend your commits to GitHub so the repo page updates.
git pullDownload any new commits from GitHub to your computer. Run before you start working.
Looking at what you and other people did
git log --onelineList all commits as one-liners. Press q to quit.
git log --oneline --graph --allSame thing, but draws the branch structure next to the commits.
git diffShow what has changed since your last commit, line by line.
git diff --stagedShow what is about to go into your next commit.
git showShow the full contents of your most recent commit.
Branches — work on a new feature without breaking main
git branchList all branches in this repo. A star marks the one you are on.
git checkout -b feature-nameCreate a new branch and switch to it in one command.
git checkout mainSwitch back to the main branch.
git merge feature-namePull the commits from feature-name into whatever branch you are currently on.
git branch -d feature-nameDelete a branch you are done with.
Undo — oh no buttons
git restore index.htmlThrow away your unsaved changes to a file. Back to the last commit.
git restore --staged index.htmlUnstage a file (undo git add) without losing your changes.
git commit --amend -m "Better message"Fix the message of your most recent commit. Only if you have not pushed yet.
git reset --soft HEAD~1Undo your last commit but keep the changes staged. You get another chance to commit.
Web browser basics — clicking, not typing
Path A equivalents for everything above. Every command has a button somewhere on github.com.
On github.com in your browser
Create a repoTop right + icon → New repository → name it → choose Public or Private → check "Add a README" → Create.
Upload filesRepo page → Add file → Upload files → drag your folder in → write a commit message → Commit.
Edit a file in the browserClick the file → pencil icon (top right) → edit → scroll down → Commit changes.
Delete a file in the browserClick the file → trash icon next to the pencil → commit the deletion.
See commit historyClick the clock-and-dots icon labeled History (on any file or at the top of the repo).
Invite a collaboratorRepo → Settings → Collaborators → Add people → type drjulsgilliam → pick me from the dropdown.
Turn on GitHub PagesRepo → Settings → Pages → Source = Deploy from a branch → Branch = main → / (root) → Save.
Change public/privateRepo → Settings → scroll to Danger Zone → Change visibility.
Download repo as ZIPRepo page → green Code button → Download ZIP. No Git install required.
Remember the core loopEdit files → commit with a clear message → your changes are live. That is 90% of what you will ever do on GitHub. On the CLI it is git add . → git commit -m "…" → git push. In the browser it is click file → pencil → Commit changes. Same thing, different button.
Need to polish the resume that goes with it?
Your GitHub link only helps if the resume it lives on is strong. Head back to the Resume Playground for the full NOVA IT resume walkthrough — classwork to bullets, bad vs. good examples, a copy-paste template, LinkedIn setup, and the final checklist.