Resources → Version Control & GitHub Basics

Version Control & GitHub Basics — Professional Development Skills

Master Git and GitHub for professional development. Save your work, collaborate with others, and build an impressive project portfolio.

💬 Git & GitHub Help

Questions about Git commands, GitHub features, or version control concepts? Get help with any aspect of professional development workflow.

🤔 Why Version Control Matters

Imagine working on a document and accidentally deleting hours of work, or wanting to try a risky change but being afraid you'll break everything. Version control solves these problems by tracking every change to your files.

What Version Control Does:

  • Backup Everything: Never lose work again - every version is saved
  • Track Changes: See exactly what changed, when, and why
  • Safe Experimentation: Try new features without fear of breaking things
  • Collaboration: Multiple people can work on the same project simultaneously
  • Professional Portfolio: Showcase your projects to employers or clients
Write Code
→
Save Checkpoint
→
Upload to GitHub
→
Share with World
💡 Real-World Example

You're building a website. Version control lets you save working versions, try adding a new feature, and if it breaks everything, instantly return to the last working version. No more "website_final_FINAL_v2_backup.html" files!

🛠️ Git vs GitHub: Understanding the Difference

Git and GitHub work together but serve different purposes. Think of Git as your local save system and GitHub as your cloud storage and showcase platform.

🔧 Git (The Tool)

What it is: Software that runs on your computer to track file changes

What it does: Creates checkpoints (commits) of your work locally

Analogy: Like having an infinite undo button with detailed save points

🌐 GitHub (The Platform)

What it is: Website that hosts Git repositories in the cloud

What it does: Stores your code online, enables sharing and collaboration

Analogy: Like Google Drive but specifically designed for code projects

🎯 Why You Need Both

Git tracks changes on your computer. GitHub stores everything online so you can access it anywhere, share with others, and showcase your work to potential employers or clients.

1Install and Configure Git

First, we'll install Git on your computer and configure it with your identity. This is a one-time setup process.

📥 Installation Steps

  • Windows: Download from git-scm.com and install with default settings
  • Mac: Install Xcode Command Line Tools or use Homebrew
  • Linux: Use your package manager: sudo apt install git
# Configure Git with your information (run these once)
git config --global user.name "Your Full Name"
git config --global user.email "your.email@example.com"
git config --global init.defaultBranch main
# Verify your configuration
git config --list

    

  


  

    
2Create Your GitHub Account and First Repository

    
GitHub is where you'll store and showcase your projects. Let's create an account and your first repository (repo).

    
    

      
🚀 GitHub Setup

      
    
        
  1. Go to github.com and create a free account
    2. 
        
  2. Verify your email address
    3. 
        
  3. Click "Create repository" or the "+" icon
    4. 
        
  4. Name it "my-first-repo" and check "Add README"
    5. 
        
  5. Click "Create repository"
    6. 
      

    


    

      
💡 Repository Naming Tips

      
Use descriptive names like "personal-website" or "expense-tracker-app". Avoid spaces (use hyphens instead). Keep names professional - this is your public portfolio!

    


    

      
      
      

    

  


  

    
3Basic Git Workflow: Your First Commit

    
Learn the fundamental Git workflow: clone, modify, add, commit, push. This is the pattern you'll use for all your projects.

    
    

      
# Clone (download) your repository from GitHub

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

      
cd my-first-repo

      
      
# Create or modify a file

      
echo "Hello, World!" > hello.txt

      
      
# Check what changed

      
git status

      
      
# Stage changes for commit

      
git add hello.txt

      
      
# Commit (save checkpoint) with descriptive message

      
git commit -m "Add hello.txt with greeting message"

      
      
# Push (upload) to GitHub

      
git push origin main

    


    

      
Modify Files

      →
      
git add

      →
      
git commit

      →
      
git push

    


    

      
🎯 Commit Message Best Practices

      
Write clear, descriptive commit messages: "Add user login feature" not "fixed stuff". Start with a verb (Add, Fix, Update, Remove) and keep under 50 characters when possible.

    

  


  

    
4Essential Git Commands

    
Master these core Git commands to handle 90% of your version control needs. Practice each one until it becomes second nature.

    
    

      
# Check status of your repository

      
git status

      
      
# See what changed in files

      
git diff

      
      
# View commit history

      
git log --oneline

      
      
# Stage all changes

      
git add .

      
      
# Undo changes to a file

      
git checkout -- filename.txt

      
      
# Pull latest changes from GitHub

      
git pull origin main

      
      
# Create and switch to new branch

      
git checkout -b feature-name

    


    

      
⚠️ Common Mistakes to Avoid

      
    
        
  • Don't commit without testing your changes first
    • 
        
  • Never force push (git push --force) unless you know what you're doing
    • 
        
  • Always pull before starting new work to get latest changes
    • 
      

    


    

      
      
      

    

  


  

    
5Branching: Safe Experimentation

    
Branches let you work on new features without affecting your main code. Think of them as parallel universes where you can experiment safely.

    
    

      
🌳 How Branches Work

      
main branch: Your stable, working code

      
feature branches: Experimental areas for new features

      
Workflow: Create branch → Make changes → Test → Merge back to main

    


    

      
# Create and switch to new branch

      
git checkout -b add-contact-form

      
      
# Make your changes and commit normally

      
git add .

      
git commit -m "Add contact form HTML structure"

      
git commit -m "Add contact form CSS styling"

      
git commit -m "Add contact form JavaScript validation"

      
      
# Push branch to GitHub

      
git push origin add-contact-form

      
      
# Switch back to main branch

      
git checkout main

      
      
# Merge completed feature

      
git merge add-contact-form

    


    

      
🎯 Branch Naming Conventions

      
Use descriptive branch names: "add-user-login", "fix-mobile-navigation", "update-homepage-design". This makes it clear what each branch is for.

    

  


  

    
6GitHub Features: Issues, Pull Requests, and Collaboration

    
GitHub provides powerful features for project management and collaboration. Learn to use these professional development tools.

    
    

      
🎫 Issues: Project Management

      
Track bugs, feature requests, and tasks. Each issue can be assigned, labeled, and discussed.

      
Example: "Add dark mode toggle to website header"

    


    

      
🔄 Pull Requests: Code Review

      
Propose changes from a branch to main. Others can review, comment, and approve before merging.

      
Workflow: Branch → Commit → Push → Create Pull Request → Review → Merge

    


    

      
👥 Collaboration Features

      
    
        
  • Discussions: Community conversations about the project
    • 
        
  • Wiki: Documentation and guides for your project
    • 
        
  • Actions: Automated testing and deployment
    • 
        
  • Releases: Package and distribute versions of your software
    • 
      

    


    

      
      
      

    

  


  

    
7Building Your Developer Portfolio

    
Your GitHub profile is your developer resume. Learn to showcase your projects effectively and build a professional presence.

    
    

      
🌟 Portfolio Essentials

      
    
        
  • Profile README: Create username/username repository with README.md
    • 
        
  • Pinned Repositories: Showcase your 6 best projects
    • 
        
  • Good README Files: Each project needs clear description and setup instructions
    • 
        
  • Consistent Commits: Regular activity shows you're actively learning
    • 
        
  • Diverse Projects: Show range of skills and interests
    • 
      

    


    

      
📝 Writing Great README Files

      
Every repository should have a README.md that includes:

      
    
        
  • Project Title and Description: What it does and why it matters
    • 
        
  • Screenshots: Show the project in action
    • 
        
  • Installation Instructions: How to run it locally
    • 
        
  • Usage Examples: How to use key features
    • 
        
  • Technologies Used: List languages, frameworks, tools
    • 
        
  • Future Improvements: What you plan to add next
    • 
      

    


    

      
      
      

    

  


  

    
🔄 Git + AI: Supercharged Development Workflow

    
Combine Git with AI tools for an incredibly powerful development experience. Here's how to integrate version control with your AI-powered projects:


    

      
🤖 AI-Powered Git Workflows

      
    
        
  • Commit Messages: Ask ChatGPT to write descriptive commit messages
    • 
        
  • Branch Planning: Use AI to plan feature branches and development strategy
    • 
        
  • Code Review: Get AI feedback on code before committing
    • 
        
  • Documentation: Generate README files and documentation with AI
    • 
        
  • Issue Templates: Create professional issue and PR templates
    • 
      

    


    

      
# AI-assisted development workflow example

      
git checkout -b feature/user-authentication

      
# Use GitHub Copilot to write authentication code

      
git add .

      
# Ask ChatGPT for a good commit message

      
git commit -m "Implement secure user authentication with JWT tokens"

      
git push origin feature/user-authentication

      
# Use AI to write pull request description

    


    

      
      
      

    

  


  

    
🎯 Your Version Control Mastery Plan

    
You've learned professional version control skills. Here's your roadmap to becoming proficient with Git and GitHub:


    

      
Week 1: Foundation

      
    
        
  • Install and configure Git
    • 
        
  • Create GitHub account and first repository
    • 
        
  • Practice basic workflow: clone, add, commit, push
    • 
        
  • Make commits daily to build the habit
    • 
      

    


    

      
Week 2: Branching and Collaboration

      
    
        
  • Create and merge your first feature branch
    • 
        
  • Write your first good README file
    • 
        
  • Create issues for project planning
    • 
        
  • Set up your profile README
    • 
      

    


    

      
Week 3+: Professional Practices

      
    
        
  • Use pull requests for all feature development
    • 
        
  • Pin your best repositories to your profile
    • 
        
  • Contribute to an open source project
    • 
        
  • Integrate AI tools into your Git workflow
    • 
      

    


    

      
🚀 Ready for the Next Level?

      
With Git and GitHub mastered, you're ready for Data & AI Integration to learn how to work with real-world data in your AI-powered projects. You'll use your new version control skills to manage data processing projects professionally.