This Git training teaches you to record changes traceably with commits, work in parallel on branches and review and merge through GitHub pull requests as a team. It suits developers, administrators and specialists who version scripts, configuration or documents. You resolve merge conflicts, undo mistakes with reset and revert, and agree a workflow that fits your team instead of memorising commands.
What you’ll take away.
- Create repositories, stage changes and write meaningful commits
- Work with branches and combine them with merge or rebase
- Read and resolve merge conflicts and fix mistakes with reset, revert and reflog
- Create and review pull requests on GitHub and use branch protection rules
- Choose a branching workflow such as trunk-based or feature branches for your own team
Your training in detail
- Who is it for?
- Developers, administrators, data teams and anyone who versions code, configuration or text together.
- Prerequisites
- Basic comfort with the command line. No programming skills required.
- Format & planning
- Suggested format: 1 to 2 days live online or on site. Scope depends on prior knowledge.
Agenda: from understanding to application
Our independently developed agenda proposal. Focus areas, lab environment and scope are agreed before booking.
Core model: working directory, staging area and repository, git init, add, commit, status, diff and log.
Branches: git switch, creating branches, fast-forward and merge commits, tags and .gitignore.
Conflicts and rebase: reading conflict markers, merge tools, git rebase and tidying history with git rebase -i.
Fixing mistakes: git restore, reset, revert, stash, cherry-pick and recovery through the reflog.
Collaborating with GitHub: remotes, push, pull, fetch, forks, pull requests, reviews and branch protection rules.
Workflows and automation: feature branch or trunk-based, commit conventions and a simple GitHub Actions run.
Suggested exercise: in a practice repository, deliberately create a merge conflict between two branches, resolve it, tidy the history with rebase and bring the change in through a pull request.
Exams, licences & credentials
There is no vendor exam for Git itself. GitHub offers its own certifications, whose current list should be checked with GitHub. Fees are only included if confirmed in the offer. Attending alone awards no vendor certification.
Vendor references & review date
Sources checked on 2026-11-03. These sources describe the technology or external exam requirements. They do not imply a partnership with NextNowa.
Your learning content
These objectives describe the training topic. The specific syllabus, duration, dates, trainer and price are agreed before booking.
Frequently asked questions
What is the difference between Git and GitHub?
Git is the version control system that runs locally on your machine. GitHub is a platform that hosts Git repositories and adds pull requests, reviews and automation. GitLab and Bitbucket are comparable platforms. The Git commands in the training apply to all of them.
Merge or rebase: which should I use?
Merge keeps the actual history and is safe for shared branches. Rebase produces a linear history but should only be used on your own, unpublished commits. Which rule applies in your team is a matter of agreement. In the training you try both and settle on one.
Can I really undo a mistake in Git?
Mostly, yes. Committed changes can be recovered through revert, reset or the reflog, because Git keeps commits for a long time. Uncommitted work is much harder to restore. That is why we practise typical mishaps in a test repository during the training.
Does Git & GitHub include a certificate?
There is no vendor exam for Git itself. GitHub offers its own certifications, whose current list should be checked with GitHub. Fees are only included if confirmed in the offer. Attending alone awards no vendor certification.