Start Using Git and GitHub Without Fear
Mohamed Sesay
Git is a history for your project. GitHub is a place where that history can be safely stored and shared. You do not need to memorise dozens of commands before you begin. Start by understanding the three actions you will repeat: save a meaningful checkpoint, share it, and review what changed.
1. Make one project folder worth keeping
Use a tiny finished project, such as the profile page from the previous guide. Give the folder a clear name such as my-profile-page. Add a README.md file with three lines: what the project is, how to open it, and what you plan to improve next.
2. Record your first checkpoint
git init
git add .
git commit -m "Create first profile page"A commit is a named snapshot, not a vague backup. Write a message that says what changed. “Fix stuff” is not useful next month; “Add contact button and mobile spacing” is useful to you and to a collaborator.
3. Change one thing safely
- Change the heading or button text.
- Run the page and check that it still works.
- Use
git statusto see exactly which files changed. - Commit the change with a specific message.
4. Publish the repository
Create a repository on GitHub, then connect your local folder and push it. If commands feel like a barrier, GitHub Desktop gives the same workflow with visible buttons. The important part is not the tool; it is learning to inspect a change before you publish it.
Never publish secrets
Do not place passwords, API keys, bank details, private student data, or .env files in a public repository. If you are unsure, pause and ask before pushing.
This guide is an original starter path based on GitHub’s official getting-started material, which describes a repository as a project folder with tracked history and recommends a clear README for each project.
Related