From 5964dde3d4d00793cc74076db84182fcaf0f96ab Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 17 Jan 2026 18:04:09 +0000
Subject: [PATCH 1/2] Initial plan


From a34c337394e584b7627ca02cbe2a95f271839cb2 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 17 Jan 2026 18:08:03 +0000
Subject: [PATCH 2/2] Add comprehensive learning resources for GitHub beginners

Co-authored-by: rmorenosalg-design <235914305+rmorenosalg-design@users.noreply.github.com>
---
 CHEAT_SHEET.md     | 211 +++++++++++++++++++++++++++++++++++++++++
 GETTING_STARTED.md |  85 +++++++++++++++++
 README.md          |  22 +++++
 TROUBLESHOOTING.md | 232 +++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 550 insertions(+)
 create mode 100644 CHEAT_SHEET.md
 create mode 100644 GETTING_STARTED.md
 create mode 100644 TROUBLESHOOTING.md

diff --git a/CHEAT_SHEET.md b/CHEAT_SHEET.md
new file mode 100644
index 0000000..f5bca8d
--- /dev/null
+++ b/CHEAT_SHEET.md
@@ -0,0 +1,211 @@
+# GitHub Quick Reference Cheat Sheet
+
+A handy reference guide for common GitHub operations and commands.
+
+## 🌐 GitHub Web Interface
+
+### Creating a New Repository
+1. Click the **+** icon in the top right corner
+2. Select **New repository**
+3. Fill in repository name and description
+4. Choose public or private
+5. Click **Create repository**
+
+### Creating a Branch
+1. Click the branch dropdown (shows "main" by default)
+2. Type your new branch name
+3. Click **Create branch**
+
+### Making Changes Through Web Interface
+1. Navigate to the file you want to edit
+2. Click the pencil icon (✏️) to edit
+3. Make your changes
+4. Scroll down to the commit section
+5. Add a commit message
+6. Click **Commit changes**
+
+### Opening a Pull Request
+1. Click **Pull requests** tab
+2. Click **New pull request**
+3. Select the branch with your changes
+4. Click **Create pull request**
+5. Add a title and description
+6. Click **Create pull request**
+
+### Merging a Pull Request
+1. Open the pull request
+2. Review the changes
+3. Click **Merge pull request**
+4. Click **Confirm merge**
+5. Optionally delete the branch
+
+## 💻 Git Command Line Basics
+
+### Setup and Configuration
+```bash
+# Set your name
+git config --global user.name "Your Name"
+
+# Set your email
+git config --global user.email "your.email@example.com"
+
+# Check your settings
+git config --list
+```
+
+### Starting a Repository
+```bash
+# Initialize a new repository
+git init
+
+# Clone an existing repository
+git clone https://github.com/username/repository.git
+```
+
+### Basic Workflow
+```bash
+# Check status of your files
+git status
+
+# Add files to staging area
+git add filename.txt        # Add specific file
+git add .                   # Add all changed files
+
+# Commit your changes
+git commit -m "Your commit message"
+
+# Push changes to GitHub
+git push origin main
+```
+
+### Branching
+```bash
+# Create a new branch
+git branch branch-name
+
+# Switch to a branch
+git checkout branch-name
+
+# Create and switch to new branch (shortcut)
+git checkout -b branch-name
+
+# List all branches
+git branch
+
+# Delete a branch
+git branch -d branch-name
+```
+
+### Updating and Syncing
+```bash
+# Get latest changes from GitHub
+git pull origin main
+
+# Fetch changes without merging
+git fetch origin
+
+# Merge a branch into current branch
+git merge branch-name
+```
+
+### Viewing History
+```bash
+# View commit history
+git log
+
+# View compact history
+git log --oneline
+
+# View changes in files
+git diff
+
+# View changes for a specific file
+git diff filename.txt
+```
+
+## 🔑 Key Concepts
+
+### The Git Workflow
+1. **Modify** files in your working directory
+2. **Stage** changes you want to commit (`git add`)
+3. **Commit** staged changes (`git commit`)
+4. **Push** commits to GitHub (`git push`)
+
+### Branch Strategy
+- **main/master**: The stable, production-ready code
+- **feature branches**: Create these for new features or changes
+- **Always branch**: Never work directly on main for new changes
+
+### Commit Message Best Practices
+- Use present tense ("Add feature" not "Added feature")
+- Keep first line under 50 characters
+- Be descriptive but concise
+- Example: "Fix login button alignment on mobile"
+
+## 📝 Common Terms
+
+| Term | Description |
+|------|-------------|
+| **Repository** | A project folder tracked by Git |
+| **Clone** | Download a copy of a repository |
+| **Fork** | Create your own copy of someone else's repository |
+| **Commit** | Save a snapshot of your changes |
+| **Push** | Upload your commits to GitHub |
+| **Pull** | Download and merge changes from GitHub |
+| **Branch** | A separate line of development |
+| **Merge** | Combine changes from different branches |
+| **Pull Request** | Propose changes to be merged |
+| **Remote** | A version of your repository hosted elsewhere (like GitHub) |
+| **Origin** | The default name for your remote repository |
+
+## 🆘 Common Issues and Solutions
+
+### Problem: Changes not showing on GitHub
+**Solution**: Make sure you've committed AND pushed your changes
+```bash
+git add .
+git commit -m "Your message"
+git push origin main
+```
+
+### Problem: Merge conflict
+**Solution**: 
+1. Open the conflicting files
+2. Look for conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`)
+3. Edit to keep the correct version
+4. Remove the conflict markers
+5. Commit the resolved files
+
+### Problem: Want to undo last commit (not pushed yet)
+**Solution**:
+```bash
+git reset HEAD~1  # Keeps changes but undoes commit
+```
+
+### Problem: Accidentally committed to wrong branch
+**Solution**:
+```bash
+git stash              # Save your changes
+git checkout correct-branch
+git stash pop          # Apply your changes
+```
+
+## 🎯 Tips for Success
+
+1. **Commit often**: Small, frequent commits are better than large ones
+2. **Write good commit messages**: Your future self will thank you
+3. **Pull before you push**: Always get the latest changes first
+4. **Branch for features**: Keep your main branch clean
+5. **Review before committing**: Use `git status` and `git diff`
+6. **Use .gitignore**: Don't commit unnecessary files
+
+## 📚 Learn More
+
+- [GitHub Documentation](https://docs.github.com)
+- [Pro Git Book](https://git-scm.com/book/en/v2) - Free and comprehensive
+- [GitHub Learning Lab](https://lab.github.com)
+- [Git Cheat Sheet (PDF)](https://education.github.com/git-cheat-sheet-education.pdf)
+
+---
+
+**Remember**: Practice makes perfect! The more you use Git and GitHub, the more natural it becomes. 🚀
diff --git a/GETTING_STARTED.md b/GETTING_STARTED.md
new file mode 100644
index 0000000..526728b
--- /dev/null
+++ b/GETTING_STARTED.md
@@ -0,0 +1,85 @@
+# Getting Started with GitHub
+
+Welcome! This guide will help you understand the basics of GitHub and get you started on your learning journey.
+
+## What is GitHub?
+
+GitHub is a web-based platform where developers store, share, and collaborate on code. Think of it as a social network for programmers, where you can:
+- Store your code projects
+- Track changes to your code over time
+- Collaborate with others
+- Share your work with the world
+
+## Key Concepts for Beginners
+
+### 1. **Repository (Repo)**
+A repository is like a folder for your project. It contains all your project files and the history of changes made to them.
+
+### 2. **Git**
+Git is the version control system that powers GitHub. It helps you track changes to your files over time.
+
+### 3. **Commit**
+A commit is like a snapshot of your project at a specific point in time. Think of it as saving your progress in a video game.
+
+### 4. **Branch**
+A branch is a separate version of your repository. You can make changes on a branch without affecting the main version of your project.
+
+### 5. **Pull Request (PR)**
+A pull request is how you propose changes to a project. It's like saying "Hey, I made some improvements. Would you like to include them?"
+
+### 6. **Merge**
+Merging is when you combine changes from one branch into another, usually from your working branch into the main branch.
+
+## Your First Steps on GitHub
+
+If you're new to GitHub, here's what you should do:
+
+1. **Create a GitHub Account**: Go to [github.com](https://github.com) and sign up
+2. **Complete This Course**: This repository is an interactive course that will teach you the basics
+3. **Follow the README**: The main README.md file has step-by-step instructions
+4. **Practice**: The best way to learn is by doing!
+
+## How This Course Works
+
+This repository uses GitHub Actions to automatically guide you through the learning process:
+
+1. You'll start by creating a branch
+2. Then you'll make a commit
+3. Next, you'll open a pull request
+4. Finally, you'll merge your changes
+
+Each step builds on the previous one, and the repository will automatically update with new instructions as you progress.
+
+## Common GitHub Terms
+
+| Term | Definition |
+|------|------------|
+| **Fork** | Creating your own copy of someone else's repository |
+| **Clone** | Downloading a repository to your computer |
+| **Push** | Sending your changes to GitHub |
+| **Pull** | Getting the latest changes from GitHub |
+| **Main/Master** | The primary branch of a repository |
+| **README** | A file that explains what your project is about |
+
+## Tips for Success
+
+✅ **Read carefully**: Each step has detailed instructions
+✅ **Take your time**: There's no rush - learn at your own pace
+✅ **Ask questions**: If you're stuck, check GitHub's documentation or community forums
+✅ **Practice regularly**: The more you use GitHub, the more comfortable you'll become
+✅ **Don't be afraid to experiment**: You can't really break anything in your own repositories
+
+## Helpful Resources
+
+- [GitHub Docs](https://docs.github.com): Official GitHub documentation
+- [Git Handbook](https://guides.github.com/introduction/git-handbook/): Introduction to Git
+- [GitHub Learning Lab](https://lab.github.com): More interactive courses
+- [GitHub Community](https://github.community): Ask questions and get help
+
+## Ready to Start?
+
+Head back to the main [README.md](README.md) file to begin your GitHub learning journey!
+
+---
+
+**Remember**: Everyone was a beginner once. Take it one step at a time, and you'll be comfortable with GitHub in no time! 🚀
diff --git a/README.md b/README.md
index 79ea84f..4a8a018 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,15 @@
 
 _Get started using GitHub in less than an hour._
 
+## 📖 Quick Navigation
+
+**New to GitHub?** Start here:
+- 📘 [Getting Started Guide](GETTING_STARTED.md) - Learn the basics and key concepts
+- 📋 [Quick Reference Cheat Sheet](CHEAT_SHEET.md) - Handy commands and operations
+- 🔧 [Troubleshooting Guide](TROUBLESHOOTING.md) - Solutions to common problems
+
+**Ready to learn?** Follow the course below!
+
 </header>
 
 <!--
@@ -29,6 +38,10 @@ People use GitHub to build some of the most advanced technologies in the world.
 - **Prerequisites**: None. This course is a great introduction for your first day on GitHub.
 - **How long**: This course takes less than one hour to complete.
 
+### 🆕 New to GitHub?
+
+If this is your first time using GitHub, we recommend starting with our [Getting Started Guide](GETTING_STARTED.md) to familiarize yourself with key concepts before beginning the course.
+
 In this course, you will:
 
 1. Create a branch
@@ -58,6 +71,15 @@ In this course, you will:
    - Scroll down and click the **Create repository** button at the bottom of the form.
 3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README.
 
+## 📚 Additional Learning Resources
+
+Once you complete this course, continue your GitHub journey with these resources:
+
+- **[Getting Started Guide](GETTING_STARTED.md)**: Quick reference for GitHub concepts and terminology
+- **[GitHub Docs](https://docs.github.com)**: Official documentation for all GitHub features
+- **[Git Handbook](https://guides.github.com/introduction/git-handbook/)**: Learn the fundamentals of Git
+- **[GitHub Skills](https://skills.github.com)**: More interactive courses to expand your knowledge
+
 <footer>
 
 <!--
diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md
new file mode 100644
index 0000000..51374eb
--- /dev/null
+++ b/TROUBLESHOOTING.md
@@ -0,0 +1,232 @@
+# Troubleshooting Guide for GitHub Beginners
+
+This guide addresses common issues that beginners encounter when learning GitHub.
+
+## 🚨 Common Problems and Solutions
+
+### 1. "I can't find where to create a branch"
+
+**Problem**: You're on the GitHub website but can't see the branch dropdown.
+
+**Solution**:
+- Make sure you're on the **Code** tab of your repository
+- Look for a dropdown button that says "main" (or "master")
+- It's usually located on the left side, above the file list
+- Click it and type your new branch name in the text field
+
+**Visual Help**: Check the `/images/main-branch-dropdown.png` in this repository for reference.
+
+---
+
+### 2. "My changes aren't showing up"
+
+**Problem**: You made changes but they're not visible on GitHub.
+
+**Solution**:
+- Did you **commit** your changes? Just editing a file isn't enough.
+- Did you **push** your changes to GitHub? Commits on your computer need to be uploaded.
+- Are you looking at the correct branch? Make sure you're viewing the branch where you made changes.
+
+**Steps to verify**:
+1. On GitHub, click the branch dropdown
+2. Select the branch where you made changes
+3. Navigate to the file you edited
+4. You should see your changes
+
+---
+
+### 3. "I don't see the 'Create pull request' button"
+
+**Problem**: You've created a branch but can't figure out how to create a pull request.
+
+**Solution**:
+- Make sure you've committed at least one change to your branch
+- Go to the **Pull requests** tab (near the top of your repository page)
+- Click the green **New pull request** button
+- Select your branch from the "compare" dropdown
+- Click **Create pull request**
+
+**Alternative**: GitHub often shows a yellow banner with a **Compare & pull request** button after you push changes to a branch.
+
+---
+
+### 4. "I accidentally committed to the main branch"
+
+**Problem**: You made changes directly to main instead of creating a new branch first.
+
+**Solution - If you haven't pushed yet**:
+```bash
+# Create a new branch with your changes
+git checkout -b my-feature-branch
+
+# Go back to main
+git checkout main
+
+# Reset main to match the remote
+git reset --hard origin/main
+```
+
+**Solution - If you already pushed**:
+- Don't panic! Your changes are safe
+- Create a new branch from main: the new branch will have your changes
+- You can then create a pull request from the new branch
+- Or, just continue working - it's okay for learning!
+
+---
+
+### 5. "Git command not found"
+
+**Problem**: When you try to use git commands in terminal, you get "command not found".
+
+**Solution**:
+- Git needs to be installed on your computer first
+- Download from: https://git-scm.com/downloads
+- After installing, restart your terminal
+- Test by typing: `git --version`
+
+**For this course**: You don't need to install Git! Everything can be done through the GitHub website.
+
+---
+
+### 6. "I can't merge my pull request"
+
+**Problem**: The merge button is grayed out or there's a message about conflicts.
+
+**Solution for conflicts**:
+1. Don't worry - this is normal!
+2. Click on the **Resolve conflicts** button
+3. GitHub will show you where the conflicts are
+4. Edit the file to keep the correct version
+5. Remove the conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`)
+6. Click **Mark as resolved**
+7. Click **Commit merge**
+
+**Solution for checks/reviews**:
+- Some repositories require approvals before merging
+- Wait for any automated checks to complete (you'll see a ✅)
+- If you're the owner, you can merge your own pull requests
+
+---
+
+### 7. "I deleted something important by mistake"
+
+**Problem**: You deleted a file or changed something you didn't mean to.
+
+**Solution**:
+- Good news: Git keeps history of everything!
+- On GitHub web: Go to the file, click **History**, find the version you want, copy the content
+- In terminal: `git checkout -- filename.txt` restores the file
+- Or: `git log` to see history, `git checkout <commit-hash> -- filename.txt` to restore from a specific commit
+
+**Remember**: This is why we commit often - it creates save points!
+
+---
+
+### 8. "The page says 'Error 404' or repository not found"
+
+**Problem**: You're getting a 404 error when trying to access your repository.
+
+**Solution**:
+- Check the URL - make sure the username and repository name are correct
+- Make sure you're logged into GitHub
+- If it's a private repository, ensure you have access permissions
+- The repository might have been renamed or deleted
+
+---
+
+### 9. "I'm confused about branches"
+
+**Problem**: The whole branch concept isn't making sense.
+
+**Analogy**: 
+Think of your main branch as the published version of a book. When you want to write a new chapter, you:
+1. Make a copy (create a branch)
+2. Write your chapter in the copy (make changes in your branch)
+3. Review it (create a pull request)
+4. Add it to the published book (merge)
+
+**Key points**:
+- Main branch = the "official" version
+- Your branch = your experimental/work-in-progress version
+- Pull request = asking to combine your work into the official version
+- Merge = actually combining it
+
+---
+
+### 10. "The terminal is asking for my username and password repeatedly"
+
+**Problem**: Git keeps asking for credentials every time you push or pull.
+
+**Solution**:
+- GitHub no longer accepts passwords for Git operations
+- You need to use a Personal Access Token (PAT) instead
+- Generate one: GitHub Settings → Developer settings → Personal access tokens → Generate new token
+- Use the token as your password
+
+**Better solution**: Set up SSH keys
+- Follow guide: https://docs.github.com/en/authentication/connecting-to-github-with-ssh
+- Once set up, you won't need to enter credentials
+
+---
+
+## 🆘 Still Stuck?
+
+### Before Asking for Help
+1. ✅ Read the error message carefully
+2. ✅ Try the solution suggested in the error
+3. ✅ Search GitHub Docs for your specific error
+4. ✅ Check if you're on the right branch
+5. ✅ Verify you're in the correct directory
+
+### Where to Get Help
+- **GitHub Community Forum**: https://github.community
+- **GitHub Docs**: https://docs.github.com
+- **GitHub Support**: https://support.github.com
+- **Stack Overflow**: Tag your question with `git` and `github`
+
+### How to Ask Good Questions
+When asking for help, include:
+1. What you were trying to do
+2. What you expected to happen
+3. What actually happened
+4. Any error messages (copy the exact text)
+5. What you've already tried
+
+**Example**:
+> "I'm trying to create a branch called 'my-first-branch' by clicking on the main dropdown, but I don't see an option to create a new branch. I'm looking at the Code tab of my repository. I expected to see a text field where I could type the branch name."
+
+---
+
+## 💡 Preventive Tips
+
+### Before You Start
+- ✅ Read all instructions completely
+- ✅ Make sure you're in the right repository
+- ✅ Check which branch you're on
+- ✅ Keep your main branch clean
+
+### Good Habits
+- ✅ Commit often with clear messages
+- ✅ Pull before you push
+- ✅ Test your changes before committing
+- ✅ Don't commit sensitive information (passwords, API keys)
+- ✅ Use `.gitignore` for files you don't want to track
+
+### When Things Go Wrong
+- ✅ Don't panic - Git rarely loses data
+- ✅ Don't force push unless you know what you're doing
+- ✅ Ask for help early - don't let frustration build up
+- ✅ Learn from mistakes - they're part of the learning process
+
+---
+
+## 📚 Additional Resources
+
+- [GitHub's Troubleshooting Guide](https://docs.github.com/en/get-started)
+- [Git Official Documentation](https://git-scm.com/doc)
+- [Oh Sh*t, Git!?!](https://ohshitgit.com) - Fixing common Git mistakes
+- [GitHub Skills](https://skills.github.com) - Interactive learning
+
+---
+
+**Remember**: Every expert was once a beginner who refused to give up. You've got this! 💪