Git & GitHub for Beginners Curriculum

Public curriculum preview for visitors and enrolled students. Use this page to evaluate module scope, outcomes, and learning path.

Curriculum

Git & GitHub for Beginners

Version control essentials. Commit, branch, merge, and collaborate.

Duration: 12 Weeks
Level: Beginner
Study Time: 3 hours/week + labs
School: Hexadigitall Academy

Welcome to Git & GitHub for Beginners! 🎓

This curriculum is designed to take you from core understanding to confident delivery through weekly applied practice, measurable outcomes, and portfolio evidence.

Each week builds progressively with practical tasks, implementation checkpoints, and reflection points so you can convert knowledge into repeatable professional performance.

Your success is our priority. Stay consistent with weekly execution, document your work, and use feedback loops to continuously improve your delivery quality.

Essential Resources

  • Project Charter template, WBS examples, and stakeholder analysis worksheets
  • Risk register, change log, and lessons learned repository templates
  • ROI calculation models, benefits tracking dashboards, and governance frameworks

Learning Roadmap

  • Early Weeks: Project fundamentals, planning, and stakeholder management
  • Middle Weeks: Execution excellence, risk management, and adaptive strategies
  • Late Weeks: Delivery validation, lessons learned, and strategic impact
  • Merging, Rebasing, and Conflict Resolution
  • Ignoring Files, Tags, and Release Snapshots
  • GitHub Repositories, Issues, and README Hygiene
  • Pull Requests and Code Review Workflow
  • Collaborative Branch Protection and Permissions
  • Managing Remote Branches and Fork-Based Contribution
  • Git Troubleshooting, Recovery, and Reflog Basics
  • Open Source Contribution Simulation
  • Capstone: Team Workflow from Issue to Merge

Detailed Weekly Curriculum

Each week includes outcomes and practical lab work aligned to the curriculum structure.

Week 1

Version Control Concepts and Repository Setup

3 hours/week + labs
Learning Outcomes
  • Identify the principles of Version Control Concepts and Repository Setup and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Version Control Concepts and Repository Setup in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Version Control Concepts and Repository Setup, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Version Control Concepts and Repository Setup with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 2

Tracking Changes with Commits and History

3 hours/week + labs
Learning Outcomes
  • Identify the principles of Tracking Changes with Commits and History and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Tracking Changes with Commits and History in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Tracking Changes with Commits and History, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Tracking Changes with Commits and History with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 3

Branching for Features and Fixes

3 hours/week + labs
Learning Outcomes
  • Identify the principles of Branching for Features and Fixes and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Branching for Features and Fixes in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Branching for Features and Fixes, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Branching for Features and Fixes with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 4

Merging, Rebasing, and Conflict Resolution

3 hours/week + labs
Learning Outcomes
  • Identify the principles of Merging, Rebasing, and Conflict Resolution and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Merging, Rebasing, and Conflict Resolution in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Merging, Rebasing, and Conflict Resolution, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Merging, Rebasing, and Conflict Resolution with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 5

Ignoring Files, Tags, and Release Snapshots

3 hours/week + labs
Learning Outcomes
  • Apply the principles of Ignoring Files, Tags, and Release Snapshots and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Ignoring Files, Tags, and Release Snapshots in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Ignoring Files, Tags, and Release Snapshots, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Ignoring Files, Tags, and Release Snapshots with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 6

GitHub Repositories, Issues, and README Hygiene

3 hours/week + labs
Learning Outcomes
  • Apply the principles of GitHub Repositories, Issues, and README Hygiene and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze GitHub Repositories, Issues, and README Hygiene in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for GitHub Repositories, Issues, and README Hygiene, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for GitHub Repositories, Issues, and README Hygiene with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 7

Pull Requests and Code Review Workflow

3 hours/week + labs
Learning Outcomes
  • Apply the principles of Pull Requests and Code Review Workflow and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Pull Requests and Code Review Workflow in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Pull Requests and Code Review Workflow, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Pull Requests and Code Review Workflow with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 8

Collaborative Branch Protection and Permissions

3 hours/week + labs
Learning Outcomes
  • Apply the principles of Collaborative Branch Protection and Permissions and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Collaborative Branch Protection and Permissions in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Collaborative Branch Protection and Permissions, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Collaborative Branch Protection and Permissions with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 9

Managing Remote Branches and Fork-Based Contribution

3 hours/week + labs
Learning Outcomes
  • Analyze the principles of Managing Remote Branches and Fork-Based Contribution and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Managing Remote Branches and Fork-Based Contribution in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Managing Remote Branches and Fork-Based Contribution, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Managing Remote Branches and Fork-Based Contribution with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 10

Git Troubleshooting, Recovery, and Reflog Basics

3 hours/week + labs
Learning Outcomes
  • Analyze the principles of Git Troubleshooting, Recovery, and Reflog Basics and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Git Troubleshooting, Recovery, and Reflog Basics in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Git Troubleshooting, Recovery, and Reflog Basics, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Git Troubleshooting, Recovery, and Reflog Basics with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 11

Open Source Contribution Simulation

3 hours/week + labs
Learning Outcomes
  • Analyze the principles of Open Source Contribution Simulation and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Open Source Contribution Simulation in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Open Source Contribution Simulation, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Open Source Contribution Simulation with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 12

Capstone: Team Workflow from Issue to Merge

3 hours/week + labs
Learning Outcomes
  • Analyze the principles of Capstone: Team Workflow from Issue to Merge and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Capstone: Team Workflow from Issue to Merge in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Capstone: Team Workflow from Issue to Merge, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Capstone: Team Workflow from Issue to Merge with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.

Capstone Projects

Project 1: Conflict Resolution Lab Repository

Create a multi-branch repository where planned merge and rebase conflicts are introduced, resolved, and documented.

  • Conflict scenarios with resolution commits
  • Merge and rebase decision notes
  • Final clean history proof

Project 2: Team Pull Request Workflow Simulation

Implement a collaborative feature using issues, pull requests, reviews, and branch protection in a shared GitHub repository.

  • Issue-linked branch and PR lifecycle
  • Reviewer feedback and revision trail
  • Protected-branch merge completion evidence

Project 3: Capstone: Issue-to-Merge Delivery Pipeline

Deliver a complete team workflow case study from planning through merge, including governance, recovery handling, and retrospective analysis.

  • End-to-end collaboration artifact set
  • Workflow governance and troubleshooting report
  • Portfolio-ready presentation and lessons learned