Git, GitHub and GitHub Actions for Developers
Two hands-on days working the way a real engineering team works — branching and rebasing without fear, pull requests that survive review, a protected main branch, and a GitHub Actions pipeline that builds, tests and releases. You leave with the pipeline you built.
- Fee
- ₹2,700
- Duration
- 2 days · 16 hours
- Each day
- 09:00 – 17:00
- Mode
- Offline / Online
Designed for
- Developers who use Git daily and still fear rebase
- Engineers joining a team with code review and CI for the first time
- Final-year students preparing for their first engineering job
- Teams standardising on GitHub and wanting one shared way of working
- QA and DevOps engineers who need to read and fix pipelines
What to bring
- A laptop with Git installed and a free GitHub account
- Comfortable writing and running code in any one language
- No prior Git theory needed — we start from how it stores things
What you walk away with
Your own repository with a protected main branch, a reviewed pull request, and a working GitHub Actions pipeline that lints, tests, caches dependencies, blocks a bad merge and cuts a tagged release — plus the recovery commands to get out of trouble without asking anyone.
Outcomes
What you will be able to do
- 01Explain what a commit actually is and why Git can never lose committed work
- 02Branch and merge confidently and resolve a three-way conflict by reading it rather than guessing
- 03Rewrite a messy branch into a reviewable history with interactive rebase
- 04Recover from a bad reset a lost branch or a wrong force-push using the reflog
View all 10 outcomes
- Find the exact commit that introduced a bug with git bisect
- Open a pull request that a reviewer can actually review and respond to review properly
- Protect a main branch with required checks and CODEOWNERS
- Write a GitHub Actions workflow with jobs matrices caching and artifacts
- Store secrets safely and authenticate to a cloud provider without long-lived keys
- Cut a tagged release through a gated environment and debug a pipeline that fails
The two days
10 hands-on sessions
2 days · 16 hours
- Foundation
- Intermediate
- Advanced
FoundationDay 1 · 09:00 – 10:15
How Git actually stores your work
- the object model and why commits are snapshots not diffs
- blobs and trees and commits
- refs and branches as pointers
- what HEAD really is
- the working tree and index and repository
- why git status says what it says
- git add as staging not saving
- reading git log properly
What you will build
A commit reconstructed by hand with plumbing commands — you create the blob the tree and the commit yourself, then check out your own handiwork.
Module 1
FoundationDay 1 · 09:00 – 10:15
How Git actually stores your work
- the object model and why commits are snapshots not diffs
- blobs and trees and commits
- refs and branches as pointers
- what HEAD really is
- the working tree and index and repository
- why git status says what it says
- git add as staging not saving
- reading git log properly
What you will build
A commit reconstructed by hand with plumbing commands — you create the blob the tree and the commit yourself, then check out your own handiwork.
Module 1
Book this workshop
This workshop runs on request, for individuals and for teams. Tell us the dates that would suit you.
Running this for a team?