Open-source project
mouredev/hello-git avatar
mouredev/hello-git

Hello Git & GitHub: A 5-Hour Spanish Course Built as a Living Repository

Curso para aprender a trabajar con el sistema de control de versiones Git y la plataforma GitHub desde cero y para principiantes.

15,243 stars4,861 forksUnknownApache-2.0

At a glance

What is it?
This Apache-2.0 licensed repository is a free, 45-lesson video course in Spanish for Git and GitHub beginners, with a companion book and a practical exercise file. Its value lies in the structured progression, not in any codebase.
Who is it for?
Adopt this if you are a Spanish-speaking beginner who prefers video lessons over reading documentation, and if you are willing to follow a single 5-hour stream rather than separately edited videos. Do not adopt it if you need a text-based tutorial, if you are an intermediate user, or if you expect hands-on exercises beyond a single collaborative file.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • mouredev/hello-git15,243 ★ · +523
Star history
Repository2026-08-222026-11-15
mouredev/hello-git14.7k15.2k

523 Stars in the last 85 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What This Repository Actually Is

The repository's core value is its sequencing. The lessons move from Git's history and installation, through basic terminal commands, then to git init, branches, add, commit, log, status, checkout, reset, alias, .gitignore, diff, stash, merge, and conflict resolution. The second half shifts to GitHub: creating a personal repository, SSH authentication, remote, fetch, pull, clone, push, forks, and pull requests. The final lessons cover Markdown, GUI tools, Gitflow, cherry-pick, rebase, and GitHub Pages with Actions. This is a full curriculum, not a random list of tips. The progression is logical: you learn to work locally before you touch a remote server, and you learn to merge before you learn to resolve conflicts. That structure is what makes it useful for a beginner who might otherwise bounce between unrelated tutorials.

The Mechanism: Timestamps, a Single Video, and a Practice File

The course is built around one YouTube video, with each lesson linked at a specific timestamp. The README lists every lesson with its start time, so you can jump to any topic without scrubbing through the whole stream. The practice component is minimal: after lesson 36, you are asked to add your username to hello.md in the repository, which simulates a real collaborative workflow. That is the only interactive exercise. The rest is watching and following along. The author also provides a channel called git-github on his Discord server for questions, which adds a community component that a static tutorial lacks. The companion book, available in print, Kindle, and ebook formats, complements the video with a 300-page theoretical-practical guide. The repository includes a notes file for the second edition, which lists updates like new sections on GitHub Actions and other commands. So the mechanism is straightforward: watch, practice with the one file, ask questions on Discord, and optionally buy the book for deeper study.

Getting Started: Commands and Configuration from the Material

The README does not include a quick-start command, because there is nothing to install from this repository. Instead, the course itself teaches the commands. From the lesson list, you can infer the sequence. You start by installing Git, then configure Git, which the course covers in lesson 5. You run git init to create a repository, git add to stage files, and git commit to save changes. You use git status and git log to inspect state. For branching, you use git branch, git switch, and git merge. For collaboration, you set up a remote with git remote, then push, pull, fetch, and clone. The README links to the official Git documentation and a cheat sheet, so you can look up exact flags. The practical exercise is to fork the repository, add your username to hello.md, and submit a pull request. That is the one concrete command flow you can reproduce. The course also covers git alias for shortening commands, and git stash for saving uncommitted work. If you follow the video, you will type these commands yourself, which is the intended way to learn.

A Real Limitation: Live-Streamed, Not Edited, and No Automated Checks

The course was recorded during live streams. That means the video may contain pauses, tangents, and mistakes that an edited tutorial would cut. For a beginner, that could be distracting, but it also mimics a real workflow where you see the instructor troubleshoot. More importantly, there is no automated exercise or quiz. The only practice is the hello.md pull request, which is a single action. You will not get feedback on whether you used the commands correctly beyond that one task. If you want to truly learn, you must create your own projects and practice repeatedly, which the course does not force. The course also assumes you are comfortable with a terminal; lesson 4 covers basic terminal commands, but if you are on Windows, you may need to adapt the iTerm and Oh My Zsh examples that the author uses on macOS. That is a potential mismatch for non-macOS users. Finally, the course is in Spanish. If you do not read or listen to Spanish, this is unusable, regardless of the repository's quality.

The Right Alternative: The Official Git Book and GitHub Docs

If you prefer text over video, the README itself links to the official Git book in Spanish, which is free and covers the same topics in more depth. The GitHub documentation also provides step-by-step guides for authentication, pull requests, and Actions. The difference in approach is significant. The video course is linear and narrative: you watch a person explain and type. The official book is reference-oriented: you read a chapter, then apply it. For a beginner who learns by doing, the video may be more engaging. For someone who needs to look up a specific command later, the book is easier to search. Another alternative is GitHub Desktop, which the course mentions in lesson 41. That is a GUI tool that removes the need to memorize commands. If you want to learn Git without the terminal, that is a valid path, but the course focuses on the command line, so you would not be following the same curriculum. The choice depends on your learning style and whether you want to understand the underlying commands or just get work done.

Maintenance and License: A Static Repository with a Clear Legal Basis

The repository is not archived, its last push was on 2026-11-02, and there are no releases. The last update mentioned is the second edition of the book in April 2024, with minor corrections. The course itself was likely recorded earlier, so the video may not reflect the latest Git or GitHub features. For example, GitHub Actions has evolved, and the course covers it only briefly in lesson 45. The notes file for the second edition adds a section on Actions and other commands, but that is in the book, not the video. The license is Apache-2.0, which allows you to use, modify, and distribute the material, provided you include the license and attribution. That is permissive, but it does not grant any trademark rights, and you cannot use the author's name to endorse a derivative work without permission. For a learner, the license means you can legally download and share the material, but you should check the book's separate terms if you buy it, since the repository license may not cover the book's content. The maintenance cost is low because there is no code to update, but the content will age as Git and GitHub change.

Who Should Skip This and What to Verify First

If you are an intermediate Git user, this course will bore you. It covers basics like git add and git commit, which you already know. If you need a text-based reference, the official docs are better. If you do not speak Spanish, do not attempt to follow along. If you prefer a hands-on, project-based course with multiple exercises, this one has only one practice file. Before you commit time, verify that the YouTube link works and that the timestamps match the current video. The README was written when the course was published, and YouTube links can break or be edited. Also check the Discord channel, because community support is a big part of the value, and it may be inactive. Finally, decide whether you want to buy the book. The repository is free, but the book costs money, and the course alone might be enough for a basic understanding. If you are a complete beginner who learns well from a single, structured video and you want a community to ask questions, this is a solid starting point. Otherwise, look elsewhere.

Editorial conclusion

Adopt this if you are a Spanish-speaking beginner who prefers video lessons over reading documentation, and if you are willing to follow a single 5-hour stream rather than separately edited videos. Do not adopt it if you need a text-based tutorial, if you are an intermediate user, or if you expect hands-on exercises beyond a single collaborative file. Before starting, verify that the YouTube link is still active and that the book's second edition notes match the video content, since the course was recorded live and may not reflect the latest Git changes.

Frequently asked questions

What is hello-git?

A five-hour, forty-five-lesson course on working with Git and GitHub from scratch, aimed at beginners, recorded live as a single video stream and indexed in the repository as forty-five timestamped links into that one recording. The cover material covers Git history and fundamentals, workflow, terminal handling, installation and configuration, more than twenty-five Git commands, GitHub from scratch, authentication, integration, collaborative flow, and tools. Everything in the repository is in Spanish.

Does hello-git contain any code?

No. The repository has six top-level entries: a licence file, a readme, a media directory, an exercise file, a notes file and a gitignore. There is no source directory, no package manifest, no build configuration and no test suite, which is why the platform reports no primary language for it. The media directory holds maximum-resolution screenshots from the companion book.

How do I practise with hello-git?

The front page sets one exercise. After watching a particular lesson on pull requests, you are asked to practise a full Git and GitHub workflow by adding your username to a document in the repository. That is the intended deliverable, which is why the repository has thousands of forks: the practice is forking and editing, not running anything.

Is there a written version of the hello-git course?

There is a separate book, sold in paperback, ebook reader and digital editions. The front page describes it as a three-hundred-page step-by-step theory-and-practice guide intended to complement the video course. A notes file in the repository records the changes between the first edition and the second, which included updated images, an added section on hosted automation and other commands, and small corrections.

Which commands does the hello-git course cover?

More than twenty-five, by the front page's count. The lesson titles name them: initialising a repository, branches, staging and committing, viewing history and status, switching and resetting, aliases, the ignore file, diffing, moving within a branch, hard reset and the reflog, tagging, the branch and switch commands, merging, conflict resolution, stashing, reintegration and deletion of branches, remotes, fetch, pull, clone, push, forking, cherry-pick and rebase, and finally hosted pages and automation.

Official sources

  1. Official README
  2. Project repository
  3. README
  4. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/mouredev-hello-git.svg)](https://hysenlabs.com/projects/mouredev-hello-git)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/mouredev-hello-git.svg)](https://hysenlabs.com/projects/mouredev-hello-git)

Was this useful?