Hello,

I was unable to do anything after the "Goal To Reach" window pops up. When I click any of the window buttons of the goal window, nothing happened. Then I tried to write down hide goal on the console; no luck either.

This error comes up on the browser console: this.goalVis is undefined

I tried this on an Ubuntu Linux, Firefox, Brave and Chrome's latest browsers. I saw the issue on every one of them

Thanks!

Kudos for the great app !

I'd like to translate it to French. Could you tell me how you'd like me to do it ? (markdowns could be a map of intl_id → vectors with current vector strings for "en_US", but what about the rest of the app ?)

Cheers,

B.

First of all, really nice job on this - this is a great way to learn and become better at git. If I wanted to show someone how to learn git, this is exactly where I would send them.

My biggest gripe right now is the amount of effort that's required to bring up the "Goal to Reach" window, as well as the fact that there's no way to keep it open while you're working on the level. At the very least, I wish there was an easy, discoverable way to bring it up with a single click.

But ideally, I'd love to see the UI more functional as a whole. You have these containers styled as OS X windows, but they're aren't movable or resizable at the moment. If they were, that would be a great way to achieve this - you could have a menu bar at the bottom where you could minimize or restore all these windows as needed. If we go this route, then this issue is basically just a duplicate of #85.

Otherwise, just going the simpler route, I would recommend that the goal window should be on the right side (so it doesn't cover up the terminal window), and when it's closed, it doesn't completely disappear out of view, but simply collapses into the sidebar - perhaps similarly to how the sidebar on http://colourco.de/ works (though maybe use click instead of hover to bring it back). Clicking on the sidebar can basically just trigger the "show goals" or "hide goals" command.

I'd be willing to try to pitch in if you like either of the ideas above.

Thanks for this great tool that I use to teach git at Paris-Dauphine University.

This request is related to #750. git 2.23 was released two and half years ago. May I suggest that it’s about time to switch the lessons to talk about git switch (and git restore where appropriate) instead of git checkout? I think that this would ease learning.

Hi, When trying to change the order of commits when doing for example git rebase -i HEAD~4 (as in level Moving Work Around:2) nothing happens. Tried this in different browsers (chrome, firefox, Internet explorer) on linux and windows pcs. And thanks for this wonderful site btw

Many projects have branch naming conventions that look something like jed/topic-name. I'm making workflow-specific levels for one such project and would like to be able to use the actual naming conventions. Is there a reason why such names are not allowed presently?

The application always start in English. The user has to close the demo window, close the level selector, figure out that little circle is an Earth icon, understand it is a locale selector, pick his language, and just then starts understanding what he's being told.

It would be superb to default the language to the browser's preferred languages setting as much as it's possible.

hi,

I clone the project and run the command grunt build to build the html files.

It gave me the following errors

....
Running "jasmine_node" task

/home/mht/learnGitBranching/node_modules/grunt/lib/util/task.js:352
          throw e;
                ^
TypeError: Cannot read property '1' of null
    at Object.<anonymous> (/home/mht/learnGitBranching/node_modules/jasmine-node/lib/jasmine-node/index.js:24:57)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (/home/mht/learnGitBranching/node_modules/grunt-browserify/node_modules/browserify/node_modules/coffee-script/lib/coffee-script/coffee-script.js:211:36)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
at Object.<anonymous> (/home/mht/learnGitBranching/node_modules/grunt-jasmine-node/tasks/jasmine-node-task.js:5:21)
    at Object.thisTask.fn (/home/mht/learnGitBranching/node_modules/grunt/lib/grunt/task.js:58:16)
    at Task.<anonymous> (/home/mht/learnGitBranching/node_modules/grunt/lib/util/task.js:343:36)
    at Task.<anonymous> (/home/mht/learnGitBranching/node_modules/grunt/lib/util/task.js:319:9)
    at /home/mht/learnGitBranching/node_modules/grunt-shell/tasks/shell.js:47:4
    at ChildProcess.exithandler (child_process.js:635:7)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at maybeClose (child_process.js:735:16)
    at Socket.<anonymous> (child_process.js:948:11)
    at Socket.EventEmitter.emit (events.js:95:17)
    at Pipe.close (net.js:466:12)

I have installed grunt-cli (from grunt tool).

I am not sure whether or not the version of grunt triggers the errors.

Thank you!

Using Windows 10 - I can interact with the UI but the console does not take any input on both Chrome and Edge.

However, when I use Firefox I can enter commands just fine

The cursor is also visible in Firefox on the console, but is not visible on the other two browsers.

Firefox:

Other:

Currently it isn't easy to get somebody to try a 3rd party lesson, they manually have to copy and past the JSON.

Would be good if this could be somehow simplified, e.g. by linking to:

http://pcottle.github.io/learnGitBranching/?tree_gist=gistid_of_json http://pcottle.github.io/learnGitBranching/?lesson_gist=gistid_of_json

and/or:

http://pcottle.github.io/learnGitBranching/?tree_url=url_to_json http://pcottle.github.io/learnGitBranching/?lesson_url=url_to_json

This would make it much easier to share problems between users, that may not necessarily be appropriate to include in this project.

Javascript security issues might be a problem, as this would require retrieving the JSON from another domain, I have a vague recollection this might not be allowed, at least not without some sort of proxy on pcottle.github.io (not even sure if that is possible).

From C1, if you run the following commands:

git commit    
git checkout C1    
git cherry-pick C2

I believe you should end up back on C2, because the cherry-pick adds exactly the same commit, with exactly the same parent.

This simulator ends up creating a clone of the C2 revision, C2'.

I believe this means the solution in "Juggling Commits 2" is incorrect, and the correct solution should be:

git checkout master
git commit --amend
git cherry-pick C3

As when you cherry-pick C2 from its parent (which seems pointless here anyway), you still end up with C2.

I find this description a bit confusing:

Technically, git clone in the real world is the command you'll use to create local copies of remote repositories (from github for example). We use this command a bit differently in Learn Git Branching though -- git clone actually makes a remote repository out of your local one. Sure it's technically the opposite meaning of the real command, but it helps build the connection between cloning and remote repository work, so let's just run with it for now.

https://github.com/pcottle/learnGitBranching/blob/a78e4d1327b8cf5eb6bcc2c0300918fab4f26419/src/levels/remote/clone.js#L71

1. I suggest to instead phrase it in one of these ways:

• Don't go into the distinction which one is the remote: "git clone is the command to create a copy of an existing repository"
• Or: invert the language: "Assume that a git repository by someone else exists somewhere (typical on another machine/server). You can use clone to get a local copy of that repository."

2. The example uses git clone without specifying a remote url. Maybe it's worth to require passing in some dummy url git clone https://example.com/myrepo.git to make the example more realistic. Or even make a small example repo on github `git clone https://github.com/pcottle/learnGitBranching-clone-example.git)/, so that the call would work in real life (and users can see the repo in GitHub - though the clone operation in the tutorial is still a dummy of course).

First of all, incredible work here. A fantastic web app for learning Git.

It looks like colors may be randomly rendered for examples to distinguish one branch from another. However, sometimes the same color is rendered for different branches:

Good Afternoon,

I would like to grab your attention towards a problem, about the visualization of the graph. It does not showup sometimes in the demonstration, on the Right-side of the curved square box while explaining about the lesson content. I am using a Brave browser. I request you to investigate & solve the bug at your earliest convenience.

Yours Faithfully, Thank you.

Hello, I have a error order history when I use the last tag in main tab.

Here we have main that is a few commits ahead of branches one two and three. For whatever reason, we need to update these three other branches with modified versions of the last few commits on main.

Blow is my git command:

$ git rebase C2 three
$ git checkout one
$ git cherry-pick C4 C3 C2
$ git checkout two
$ git cherry-pick C5
$ git rebase two one

The history of branch one should be:

C2``->C3``->C4``->C5`->C1->C0