How to Use GitHub: A Practical Guide for Beginners

GitHub is where developers store code, track changes, and collaborate. If you are new to GitHub, this guide walks you through the essentials without extra noise.

Git vs GitHub (quick clarity)

• Git is the version control tool that tracks changes on your computer.
• GitHub is the online platform that hosts Git repositories and adds collaboration features.

You can use Git without GitHub, but GitHub makes sharing and teamwork easy.

Step 1: Create your account and secure it

1. Sign up at GitHub.com.
2. Pick a professional username (you will share it often).
3. Enable two-factor authentication in Settings for account security.

Step 2: Install Git and set your identity

Install Git from git-scm.com, then set your name and email:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

This name and email appear in your commit history.

Step 3: Create your first repository

Option A: Create on GitHub (fastest)

1. Click New on GitHub.
2. Name your repository (e.g., my-first-repo).
3. Add a README.
4. Click Create repository.

Option B: Create locally and push

mkdir my-first-repo
cd my-first-repo
git init
echo "# My First Repo" > README.md
git add .
git commit -m "Initial commit"
git branch -M main
git remote add origin https://github.com/USERNAME/my-first-repo.git
git push -u origin main

Step 4: Clone and make changes

To work on a repository, clone it:

git clone https://github.com/USERNAME/my-first-repo.git
cd my-first-repo

Edit files, then run:

git add .
git commit -m "Describe what changed"
git push

Step 5: Use branches for safe updates

Branches keep your main branch stable.

git checkout -b feature/update-readme
git add README.md
git commit -m "Update README"
git push -u origin feature/update-readme

On GitHub, open a Pull Request to review and merge the branch.

Step 6: Understand pull requests

Pull requests are how teams review changes before merging:

• Summarize what changed and why.
• Keep changes small and focused.
• Request review if you are collaborating.

Step 7: Use Issues to plan work

Issues are lightweight task trackers:

• Bug reports
• Feature ideas
• Checklists for larger tasks

Step 8: Add a README and LICENSE

Good repositories explain themselves:

• README: what the project is, how to use it, how to contribute.
• LICENSE: what others are allowed to do with your code.

Step 9: Add a .gitignore

Do not commit secrets or build artifacts. Add a .gitignore so files like node_modules/ or .env stay local.

Common mistakes to avoid

• Committing API keys or passwords.
• Working directly on main for big changes.
• Writing vague commit messages like "update".
• Skipping pull requests on team projects.

Quick GitHub workflow (cheat sheet)

git clone <repo-url>
git checkout -b <new-branch>
git add .
git commit -m "Clear message"
git push -u origin <new-branch>
# Open a pull request on GitHub

Final tips for clean, AdSense-friendly content

• Write original READMEs and project docs in your own words.
• Respect licenses when you use third-party code.
• Keep your public repositories organized and professional.

Next steps

Once you are comfortable, explore:

• GitHub Projects for planning
• Actions for automation
• Markdown for better documentation

GitHub gets easier with practice. Start small, commit often, and keep your history clean.