# learn-github is a course directory, and its folders are the syllabus > learn-github is a beginner oriented teaching repository for Git and GitHub: a README that summarises the ground, a materials directory holding the long form notes, and several practice folders beside them. It is worth reading as a learning path, and less useful as a reference once you already work in a team, because the explanations stay at the level of a first repository. **drshahizan/learn-github** — A step-by-step guide to getting started with Git and GitHub for beginners. - Repository: https://github.com/drshahizan/learn-github - Stars: 1,050 · Forks: 695 - Language: Unknown - License: not declared - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/drshahizan-learn-github ## The folders are the course, not the README The repository is a teaching collection rather than a program, and the quickest way to see that is the top level of the tree. Alongside the README sit README0.md and README1.md, an `images/` directory for the artwork, and four directories whose names point at the practice side of the course: `latihan/`, `projek/`, `task/` and `tmp/`. There is a `materials/` directory that the README links into repeatedly for the actual reading. The project description calls it a step by step guide to getting started with Git and GitHub for beginners, and the README opens by welcoming readers to a GitHub class. None of the folders is described in the documentation beyond its name, which is the first thing to know as a reader: the structure implies exercises, a sample project, assignments and a scratch area, but the text does not tell you what to run or in what order, so a newcomer will need to open the directories themselves to see the shape of the work. ## The README summarises the notes instead of replacing them Every explanatory section in the README is a summary that ends with a pointer to a longer file. The Git section explains that Git is a distributed version control system created in 2005 by Linus Torvalds, that it is open source, and that it lets a team track changes, branch, merge and roll back, and then links to `materials/git-intro.md` for more. The GitHub section does the same job, listing repositories, pull requests, issues and collaboration as the key features, and linking to `materials/github-intro.md`. Two other links sit at the top: a case study under `materials/case_study.md` and a GitHub Education page under `materials/education`. So the README is an index with a short introduction attached, and the value of the repository is in what those linked files contain. If you are evaluating it as a reference, the linked notes are the part to read, not the landing page. ## The teaching order runs from a local repository to Actions The progression the README describes is a curriculum in miniature, and it is the clearest statement of what the course covers. Learners are first introduced to Git and GitHub early on the developer roadmap as a foundational skill: they set up a Git repository, make commits, and push changes to a remote repository on GitHub, and they pick up basic commands such as branching, merging and rebasing. As they progress, the guide moves to the more advanced GitHub side, where pull requests are used for code review, Git is integrated with continuous integration and continuous deployment pipelines, and workflows are automated with GitHub Actions. The order matters for judging the repository as a course: it starts where a beginner actually is and ends at the point where the platform starts to earn its keep. What it does not go near is the internals of how Git stores objects, or how to design a branching strategy for a team, and neither is mentioned. ## Roadmap sites fill in the wider learning path Alongside its own notes, the guide leans on an external roadmap site. Roadmap.sh is described as providing roadmaps for topics such as programming languages, web development and data science, laid out as step by step guides of the skills, tools and concepts needed to become proficient, and the site is said to have been created for people starting out in technology or switching careers. The README calls the roadmaps flexible and customisable so users can choose their own path and goals, and it points at the additional resources the site carries, such as books, online courses and tools, and at the community where learners exchange tips. Three concrete roadmaps are linked: frontend, backend and Flutter. The dependency is worth noting for anyone planning to use this repository as a curriculum, since a course built on top of it is also built on a third party site that can change its content without any change here. ## GitHub Education is the part that costs the reader nothing One section covers a program rather than a tool. GitHub Education is described as supporting students and educators with free access to a range of tools and resources for learning, teaching and collaborating on coding projects, and the listed benefits include free access to GitHub Enterprise and GitHub Pro, a host of developer tools, and access to courses, webinars and learning resources. The stated aim is to connect students and teachers around the world. Practically, this is the section that a reader on a student account should look at first, because the free tier it describes is the difference between being able to run a private repository with the platform's own features and being limited to what a personal account allows. The documentation gives no eligibility rules or application steps, so the practical details live in the linked `materials/education` file or on the program pages themselves. ## A first pass through the guide, without a command to run There is no install step here, because there is nothing to install: the repository is documentation, and the way to consume it is to read it in the order the README lays out. Start with the Git section, since the concepts of tracking changes, branching and merging are the foundation everything else rests on, then move to the GitHub section for repositories, pull requests, issues and collaboration, and follow the links into `materials/git-intro.md` and `materials/github-intro.md` for the full notes. The case study under `materials/case_study.md` is the natural next read, because it shows the workflow applied to something concrete, and the roadmap links are the right stopping point if you want to know what to learn after this. Along the way, the entries in `materials/` are the ones to check for currency, and the practice folders are where the hands-on part lives. The same guide also names the graphical clients that exist for people who prefer them to the command line, listing GitHub Desktop, Sourcetree and GitKraken, so a beginner who is not ready for a terminal still has a way in. ## What the guide leaves out, and how fresh it is Two gaps are visible from the documentation alone. First, the scope stops at an introduction: the README explains what pull requests and issues are for and that GitHub Actions exists, but there is no walkthrough of writing a workflow file, no coverage of rebasing conflicts, and no guidance on repository settings, permissions or protected branches, which are exactly the things a team needs on day one. Second, the repository states no licence and has no published releases, and the tree even carries a `.DS_Store` file and an `.Rhistory` file, both signs of a working folder that was committed without tidying. On freshness, the repository is not archived and its last push was on 2026-06-14, so it is not abandoned, but for a guide about a hosting platform that changes its interface regularly, a reader should check any interface claims against current GitHub documentation before teaching from it. ## Conclusion learn-github suits a learner who has just installed Git and wants one ordered place that explains what a repository is, what a pull request does and how GitHub Actions fits into a workflow, and it suits a teacher who wants notes to point students at rather than write from scratch. It does not suit an engineer who needs reference material on rebasing, conflict resolution or the finer points of Git internals, because the notes stay at introductory level and the practice folders are not described in the documentation, and it does not suit a team that needs licensing clarity before reuse, since no licence is stated for the repository. Before you build a course around it, check three things: that the linked note files under `materials/` still cover what you intend to teach, that the `latihan/`, `projek/` and `task/` folders hold what their names suggest, since the README does not describe them, and that the notes still match current GitHub, given that the last push to the repository was on 2026-06-14. ## FAQ ### What is learn-github and who is it for? It is a step by step teaching repository for beginners learning Git and GitHub, built around a README that summarises the ground and a materials directory holding the long form notes on Git, GitHub, a case study and the GitHub Education program. It is aimed at students and educators rather than experienced practitioners. ### What does learn-github teach first? The order runs from setting up a Git repository, making commits and pushing to a remote repository on GitHub, through basic commands such as branching, merging and rebasing, and then to pull request review, continuous integration pipelines and automating workflows with GitHub Actions. ### Where are the longer notes kept in learn-github? In the materials directory. The README links to `materials/git-intro.md` for the fuller Git notes, `materials/github-intro.md` for the GitHub notes, `materials/case_study.md` for a worked example, and a `materials/education` page about the GitHub Education program. ### Does learn-github need to be installed? No. It is a documentation repository with no program to run, so it is consumed by reading the README and the linked files in the materials directory, then working through the practice folders that sit beside them. ### What are the latest changes to learn-github? The repository is not archived and its last push was on 2026-06-14. It publishes no GitHub releases, so there is no tagged version to compare against when checking whether a note is current. ## Sources - [drshahizan/learn-github on GitHub](https://github.com/drshahizan/learn-github) - [Issues](https://github.com/drshahizan/learn-github/issues) - [README](https://github.com/drshahizan/learn-github/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/drshahizan-learn-github