pcottle/learnGitBranching
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
pcottle/learnGitBranching
LearnGitBranching is a popular, actively maintained interactive Git visualization and tutorial app. It targets learners who want hands-on practice with Git commands through sandbox mode, levels, challenge tracking, and shareable command URLs. The repo appears fork-friendly because it is MIT-licensed, has a large contributor surface, and recently accepted community additions such as i18n and UX/message improvements.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
This fork is not a differentiated alternative to upstream; it is best treated as an outdated mirror. Most adopters should prefer upstream unless they specifically need this exact historical snapshot.
Choose this fork if Hungarian language support is the main requirement. Choose upstream if you want the latest maintenance, fixes, and broader community improvements.
Prefer upstream unless you specifically need an old, frozen snapshot. This fork adds no visible functionality and is materially behind current upstream maintenance.
Choose this fork only if its localization and customized lesson content are the goal; otherwise upstream is the better default because it is much newer and actively maintained.
Prefer this fork only if its localization or lesson customizations matter more than staying current. For general adoption, upstream is the safer choice because this fork is stale and significantly behind.
Prefer upstream unless you specifically want this exact fork identity or the README tweak. For most users, the fork adds no meaningful capability and is materially behind current upstream work.
Prefer upstream unless you specifically want a dormant fork as a personal starting base. This fork does not show added capabilities, and it is far behind upstream.
Do not prefer this fork for normal use. It is effectively an outdated copy of upstream with no added capabilities and substantial lag behind current upstream maintenance.
Prefer upstream unless you explicitly need this fork as a private scaffold. It adds nothing visible, is far behind upstream, and is not a good choice for adopters looking for maintained improvements.