skills/introduction-to-github: A Hands-On GitHub Exercise for First-Time Users

What Introduction to GitHub Is and Who It Is For

Introduction to GitHub is a GitHub Skills exercise, which is a type of guided tutorial hosted entirely on GitHub itself. The exercise lives in the skills/introduction-to-github repository and is designed to be copied to a learner's own GitHub account as a template. Once copied, GitHub Actions automates the feedback loop: completing each step in the repository triggers the next instruction automatically.

The README states the intended audience directly: new developers, new GitHub users and students. No prerequisites are required. The README describes the exercise as "a great introduction for your first day on GitHub." The time commitment is under one hour. The exercise teaches four specific operations: creating a branch, committing a file, opening a pull request and merging that pull request. It does not teach Git command-line usage, local repository management, rebasing, merge conflict resolution or any other topic beyond those four operations.

The profile README is the exercise's output: participants build a short Markdown file that can serve as their GitHub profile README. This gives the exercise a practical result rather than producing a throwaway artifact.

The Four Steps the Exercise Covers

The exercise structure is sequential and linear. Each step must be completed in order, and GitHub Actions validates each step before revealing the next instruction. The four steps are: create a branch, commit a file, open a pull request and merge the pull request.

Creating a branch introduces the concept that changes in GitHub happen on branches before being merged into the main codebase. Committing a file introduces the idea that changes are saved as discrete snapshots with descriptive messages. Opening a pull request introduces the GitHub workflow for proposing changes: a pull request lets collaborators review changes before they become permanent. Merging the pull request introduces how changes move from a branch back into the default branch.

These four concepts cover the core read-write workflow on GitHub without introducing the command line. A participant who completes the exercise will have done each step at least once using the GitHub web interface. The README notes this takes under an hour for most participants, with GitHub Actions preparing each step in approximately 20 seconds.

How to Start: Copying the Template to Your Account

Starting the exercise requires a GitHub account and no other tools. The README provides a button that links to the GitHub repository creation page with the template pre-configured. The link sets the template_owner to skills, the template_name to introduction-to-github, and pre-fills the repository name as skills-introduction-to-github. The recommended settings from the README are: create a public repository (private repositories consume GitHub Actions minutes from the account's quota) and use your personal account as the owner.

After copying the template, the README instructs users to wait approximately 20 seconds before refreshing the page. During those 20 seconds, GitHub Actions runs the workflow that prepares the first lesson content. If the repository is not ready after 20 seconds, the README advises checking the Actions tab to see if a job is still running. A failed job indicates a bug, and the README suggests opening an issue in the template repository.

The repository has no configuration files or code to run locally. The entire exercise happens in the GitHub web interface through the repository's issues, pull requests and code editing features.

The Role of GitHub Actions in the Exercise

GitHub Actions is central to how the exercise delivers feedback. The .github/ directory in the repository contains the workflow definitions that power the exercise automation. When a participant completes a step (creates a branch, commits a file, opens a pull request or merges a pull request), a GitHub Actions workflow triggers and evaluates whether the step was completed correctly. If successful, the workflow updates the repository with the instructions for the next step.

This approach means the exercise requires no instructor and no human reviewer. The automation handles all feedback delivery. For GitHub to run these workflows, the repository needs to have GitHub Actions enabled, which it does by default for public repositories. The README notes that private repositories will use Actions minutes from the account's quota, which is why a public repository is recommended.

The automation also means the exercise is self-healing to some degree: if a participant makes a mistake, the workflow can detect the incorrect state and provide guidance. The troubleshooting advice in the README (check the Actions tab for running or failed jobs) is consistent with this design: participants debug the exercise the same way a developer debugs a CI failure.

What Introduction to GitHub Does Not Teach

The exercise covers only the GitHub web interface and only four operations. Several important topics are deliberately outside scope. Git as a command-line tool is not covered: participants never run git clone, git commit, git push or any other git command. The difference between Git and GitHub is not explained. Local development workflows, IDE integration with GitHub, merge conflicts, rebasing, code review best practices and GitHub's project management features are all outside the scope of this exercise.

The Markdown file built during the exercise is a minimal profile README. The exercise does not teach Markdown syntax in depth or explain what makes a good profile README. Participants who want to go further with profile README design will need a different resource, such as the rzashakeri/beautify-github-profile repository, which is a separate curated guide for that topic.

The README also does not cover SSH key setup, personal access tokens or any authentication method beyond the GitHub web interface's built-in session. Engineers who want to clone repositories locally and push changes will need to set up authentication outside of this exercise.

Alternative Learning Paths for GitHub and Git

GitHub Skills publishes many exercises beyond Introduction to GitHub. The organization's other repositories cover topics like GitHub Actions, GitHub Pages, code review workflows and communicating with Markdown. Each follows the same template-based, automation-driven format as Introduction to GitHub. These cover the next level of GitHub functionality after the basics introduced here.

For learning Git's command-line interface rather than the GitHub web interface, the standard reference is the Pro Git book, available free online at git-scm.com/book. Pro Git covers everything from initial setup through advanced topics like rebase, bisect and submodules. GitHub's own documentation at docs.github.com provides reference material for every GitHub feature. The difference between this exercise and those resources is interactivity: Introduction to GitHub requires the participant to actually complete each action in a real repository, while documentation requires the reader to set up their own context.

For developers who learn from video, GitHub provides a YouTube channel with tutorials, and third-party platforms offer structured Git and GitHub courses with video walkthroughs that are more comprehensive than this exercise.

Repository Status and MIT License

The last push to the skills/introduction-to-github repository was on 2026-06-22. There are no GitHub releases. The repository is maintained by GitHub under the skills organization. The top-level structure is minimal: .github/, .gitignore, LICENSE and README.md. The .github/ directory contains the GitHub Actions workflow files that drive the exercise automation.

The license is MIT. MIT allows unrestricted use, modification and redistribution with the only requirement being that the license and copyright notice are preserved. Because the repository is a template, copying it to your own account as part of the exercise creates a separate repository that you own. That copy is independent of the original template: changes to the template after you copy it do not automatically update your copy.

The README ends with a copyright notice for 2026 GitHub and links to the Contributor Covenant Code of Conduct and the MIT License. The exercise is maintained as part of GitHub's official learning resources and the GitHub Skills program.

Editorial conclusion

Students and new developers making their first contact with GitHub will find this exercise a clear and structured introduction. It covers exactly four operations (branch, commit, pull request, merge) and nothing else. Engineers who already know Git and GitHub basics will not find new material here. The exercise is free to use, and the repository is licensed MIT. The last push was on 2026-06-22. To start, copy the template to your own GitHub account using the link in the README and wait about 20 seconds for GitHub Actions to prepare the first step.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. skills/introduction-to-github on GitHub