Git and GitHub Basics for My Portfolio

Git helps me track changes, and GitHub helps me share my work publicly.

Workflow I use

I edit files, check what changed, commit with a clear message, and push to GitHub. This creates a history of my learning and project improvements.

Git is local version control. GitHub is a remote platform where I can store and share repositories. I can use Git without GitHub, but GitHub makes it easier to publish my work and show it to others.

Commands

git status shows changes. git add stages files. git commit records a snapshot. git push uploads the work.

Simple workflow example

Edit a lab README file.
Run git status to see what changed.
Run git add README.md to stage the file.
Run git commit -m "Document VLAN lab".
Run git push to upload the commit.

Portfolio habit

For each project, I include a README with objective, setup, tools, screenshots, test results, and lessons learned. The README is often the first thing a recruiter sees.

Commit message habit

A clear commit message explains the change in a few words. “Update files” is not very helpful. “Add Wireshark DNS lab notes” is better because it describes the work.

What I avoid

Committing passwords, API keys, or private information.
Uploading random files without explanation.
Leaving project READMEs empty.

Lesson learned

Small commits with clear messages are easier to understand than one huge upload at the end.