XXxxbondsxx·Sep 18, 2024
Hello, author here :) It's actually not based on geolocation, I just directly look at navigator.language / navigator.browserLanguage:
https://github.com/pcottle/learnGitBranching/blob/main/src/j...
In Learn Git Branchingpcottle
learnGitBranching
JavaScript2013–2024
pcottle / learnGitBranching
learnGitBranching
An interactive git visualization and tutorial. Aspiring students of git can use this app to educate and challenge themselves towards mastery of git!
6Distinct people
9Mentions
0Explicit recommenders
34.2KGitHub stars
What to know before exploring
What it is
An interactive git visualization and tutorial. Aspiring students of git can use this app to educate and challenge themselves towards mastery of git!
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year9 dated mentions
Observed mentions: 2013-02-16 21:05:00 UTC to 2024-09-18 13:46:49 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
9 sourceshttp://pcottle.github.io/learnGitBranching/
This should be an interactive tutorial with visualization. It is currently broken for me (Chrome-Linux).
There is screenshot on Github:
https://github.com/pcottle/learnGitBranching
In Gitless: experimental version control systemOn the off-chance that you are not trolling: The site requires JavaScript.
On the on-chance that you are trolling:
You go to the repository and raise an issue regarding the fact that there is no obvious "This site requires JavaScript" message for those who access the site without JS.
https://github.com/pcottle/learnGitBranching/issues/107
You're welcome.
In Learn Git BranchingI find this 'intro app' much more engaging: https://github.com/pcottle/learnGitBranching
In Try GitDiscussion here, I'm updating as we speak:
https://github.com/pcottle/learnGitBranching/issues/6
In Learn Git BranchingThat's a good point. I should just disable revert in all levels except for those related to it. I rarely revert in practice so it's not a huge issue.
Showing the concept of a "modified" commit is hard though. That's why I did all the C1' sillyness (like the man pages do). The apostrophes also scale nicely (up to C1'^99) where reverting a reverted rebased commit might make the text too big.
EDIT:
Fixed, see:
https://github.com/pcottle/learnGitBranching/issues/7
In Learn Git BranchingThanks a ton for catching this. I guess there is a distinction to be made -- the compression might use delta's, but a commit specifies the entire state of the repository.
It's a tricky line to walk though, because commands like "git show" and "git patch" clearly show the delta-like nature of a single commit. I also don't want newcomers to think that commits are heavy and should be used sparingly.
I'm totally down to discuss this on a github issue with you, we could go over the wording. Maybe something like "a commit specifies the entire state of a repository, but is usually stored on disk as a set of changes"?
EDIT: moving discussion to:
https://github.com/pcottle/learnGitBranching/issues/6
EDIT: fixed in:
https://github.com/pcottle/learnGitBranching/commit/168852b2...
In Learn Git BranchingLooks like raphael
https://github.com/pcottle/learnGitBranching/tree/master/lib
In Learn Git Branching