Git & GitHub Explained Like You're a Beginner

Everything you need to know to collaborate on real-world projects.

By NextPeer Editorial · 2 min read

Git and GitHub serve different purposes

Git records changes to files so you can inspect history and collaborate. GitHub hosts repositories and provides collaboration features such as pull requests and issues. You can use Git locally without uploading a repository.

Start with a small practice repository

Create a folder containing a README and a simple program. Run the following commands from that folder. Replace the example message with a description of your actual change.

git init
git status
git add README.md
git commit -m "Add project introduction"

git status tells you what changed. git add stages the files you choose. git commit records those staged changes in history. Review files before staging; avoid adding passwords, API keys or private data.

Inspect changes before committing

Use git diff to review unstaged changes and git diff --staged to review staged changes. Use git log to inspect commits. A small, focused commit is easier to review and undo than a large unrelated collection of edits.

Work on a branch

git switch -c improve-readme
git add README.md
git commit -m "Document project setup"

A branch lets you develop a change separately from the main line. When collaborating, publish the branch to the correct remote and open a pull request explaining what changed and how you checked it.

Push and pull with care

After connecting a remote repository, git push uploads your commits. git pull retrieves and integrates remote changes. Read the command output and understand the branch you are updating. Avoid force-pushing a shared branch unless the team has explicitly agreed on that workflow.

Resolve conflicts deliberately

A conflict means Git needs help combining edits. Read both versions, preserve the intended behaviour and remove conflict markers. Run the relevant checks before committing the resolution. Ask your teammate when the correct outcome is unclear.

Keep a useful README

Document the project purpose, requirements, installation, usage and known limitations. Include a screenshot or demo link when it helps. Another person should be able to run the project using your instructions.

First collaboration exercise

Open an issue for a small improvement, create a branch, make one change and open a pull request. Review the diff as if you were the maintainer. This develops a habit of understandable, reviewable work.